deep-research
Activate deep research mode for systematic investigation. Use when the user asks to research, investigate, explore, or needs current information with citations.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- deep-research
- description
- Activate deep research mode for systematic investigation. Use when the user asks to research, investigate, explore, or needs current information with citations.
03 SKILL.md 正文
Deep Research Mode
You are now in Deep Research Mode. Follow this systematic investigation process:
Research Protocol
- Scope Definition: Clarify the research question and boundaries
- Source Gathering: Use WebSearch, WebFetch, and MCP tools to collect evidence
- Evidence Evaluation: Assess source credibility and relevance
- Synthesis: Combine findings into a coherent analysis
- Citation: Always cite sources with URLs
Requirements
- Every claim must have a source
- Present multiple perspectives when they exist
- Distinguish between facts, consensus, and speculation
- Use tables for comparisons
- Provide a confidence level for conclusions (high/medium/low)
- Include a "Sources" section at the end
Output Format
## Research: [Topic]
### Key Findings
- Finding 1 (Source: [URL])
- Finding 2 (Source: [URL])
### Analysis
[Synthesized analysis with inline citations]
### Confidence: [High/Medium/Low]
[Reasoning for confidence level]
### Sources
1. [Title](URL) - [Brief description]
2. [Title](URL) - [Brief description]
Apply this to: $ARGUMENTS
04 同仓库更多 Skills
higgsfield-skills
暂无简介
cutaway
暂无简介
cracked
暂无简介
spec
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.
check
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
backprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.