deep-research
Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- deep-research
- description
- Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.
03 SKILL.md 正文
deep-research — cited, cross-checked web research
Use this for any question that needs current, verifiable information from the web. The deliverable is a synthesized answer where every load-bearing claim is backed by a source you actually read.
Tools
search_web_pages(query, [site], [published_after], [published_before], [mode])— discover candidate sources. Write thequeryas a natural-language description of the ideal page, not keywords. Usemode: pro(default).fetch_page_content(url, [max_chars])— read the full page (markdown). A search snippet is NEVER sufficient evidence — fetch before you cite.
Procedure
- Plan. Break the question into 3-6 focused sub-queries that together cover it. For contested or high-stakes questions, plan at least two independent angles.
- Search. Run
search_web_pagesper sub-query. Prefer primary sources; usepublished_afterfor anything time-sensitive. - Read.
fetch_page_contenton the 2-3 most promising results per sub-query. Quote/cite only what you read, not what a snippet implied. - Cross-check. Verify every load-bearing claim against ≥2 INDEPENDENT sources (independent = different owners, not mirrors of one another). When sources disagree, surface the disagreement rather than picking silently.
- Synthesize. Write a structured answer. Each non-obvious claim gets an inline citation to the URL you fetched. Separate "well-supported" from "uncertain / single-source".
- Cite. End with a
Sourceslist of the URLs you actually fetched.
Notes
- Don't answer from prior knowledge with a disclaimer — search and read first.
- If coverage is thin or sources conflict irreconcilably, say so explicitly; an honest "the evidence is mixed" beats false confidence.
- Keep each sub-query narrow enough that a couple of fetches resolve it.
04 同仓库更多 Skills
deep-research
Research checklist and source-quality guidance for the archer e2e fixture.
pi-e2e-xyz-greet-c4a8d5
Test greeter — pi skills e2e. The unique suffix c4a8d5 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.
pi-e2e-xyz-count-d2f6e1
Test counter — pi skills e2e. The unique suffix d2f6e1 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.
pi-e2e-xyz-greet-c4a8d5
Test greeter — pi skills e2e. The unique suffix c4a8d5 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.
pi-e2e-xyz-count-d2f6e1
Test counter — pi skills e2e. The unique suffix d2f6e1 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.
pi-e2e-xyz-greet-c4a8d5
Test greeter — pi skills e2e. The unique suffix c4a8d5 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.