Scholarsearch
PassAudited by ClawScan on May 1, 2026.
Overview
Scholarsearch appears to be a coherent academic-search helper, but users should verify the command setup, API/account access, Feishu delivery, Obsidian saving, and any optional schedule before use.
Before installing or using this skill, verify what `scholarsearch` command will run, use scoped credentials for Tavily or Feishu if needed, choose a specific Feishu destination, confirm the Obsidian save path, and only enable daily scheduling if you want recurring automated reports.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user or agent might run a local command whose implementation is not included in the reviewed artifact set.
The skill documents invoking a local `scholarsearch` command, while the supplied artifacts provide no install spec or code for that command. This is purpose-aligned and user-directed, but its provenance should be verified.
`scholarsearch 关键词：房颤，导管消融，脉冲电场消融`
Confirm the source and contents of any `scholarsearch` executable or wrapper before using it, and prefer a pinned, documented installation source.
If credentials are needed, they could grant access to search APIs or a Feishu workspace depending on how the user configures them.
These integrations may involve API keys or account permissions, but the registry metadata declares no primary credential or environment variables. No artifact shows credential leakage or misuse, so this is a setup-scope note.
`Tavily API: Academic web search with PubMed/Scholar support` and `Feishu: Daily delivery of complete briefing content`
Use narrowly scoped API tokens or workspace permissions, avoid sharing credentials in prompts, and document how Tavily and Feishu authentication should be provided.
Search topics and generated literature summaries may be shared outside the local environment with whichever Feishu destination is configured.
The skill discloses that complete generated briefings can be sent to Feishu, an external collaboration service, but it does not specify the target chat/channel or workspace boundaries.
`Dual delivery: Saves to Obsidian + sends complete content via Feishu`
Configure the Feishu recipient explicitly, review whether the briefing content is appropriate to share, and avoid sending sensitive research topics to broad channels.
The academic briefings may remain in the user's notes and could influence future work if treated as authoritative without verification.
The skill writes generated summaries into a persistent local notes location. The path is scoped and purpose-aligned, but users should remember these generated summaries may be reused or trusted later.
`Obsidian: Auto-save to Obsidian 每日学术更新/YYYY-MM-DD.md`
Keep the save path scoped, label generated reports clearly, and verify important citations or medical/scientific claims before relying on them.
If scheduled, the workflow may repeatedly search, save, and send reports until the schedule is disabled.
The skill suggests optional recurring execution. This is disclosed and aligned with morning briefings, but a schedule would let it run and deliver reports without a fresh manual invocation each time.
`For automatic scheduling: Use cron or heartbeat to run at 5:00 AM daily`
Only enable cron or heartbeat intentionally, keep logs, set clear stop conditions, and know how to disable the schedule.