Speq ext research
External documentation and research via Context7 and WebSearch — library APIs and design patterns. Triggered by /speq-mission, /speq-implement, planner-agent, implementer-agent, and implementer-expert-agent when current external sources are needed.From its SKILL.md
npx -y skills add marconae/speq-skill --skill speq-ext-researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 3 commands, including `resolve-library-id` and 2 more.
SKILL.md
1.4 KB, 282 tokens by cl100k_base, as published. Nobody here has run it
External Research
External documentation and research via Context7 and WebSearch.
When to Use
| Source | Use For |
|---|---|
| Context7 | Library APIs, method signatures, usage examples |
| WebSearch | Design patterns, architecture decisions, best practices |
Context7 Workflow
1. resolve-library-id
query: "<what you need>"
libraryName: "<library name>"
2. query-docs
libraryId: "<from step 1>"
query: "<specific question>"
WebSearch Workflow
1. WebSearch(query: "<design question>")
2. Extract relevant patterns
3. Apply to implementation
Priority Decision
Apply an evidence hierarchy — primary documentation over secondary commentary:
Need library API details?
├─ Yes → Context7
└─ No → Need design guidance?
├─ Yes → WebSearch
└─ No → Proceed with existing knowledge
Example
Adding rate limiting to Express API:
1. resolve-library-id
query: "Express.js rate limiting"
libraryName: "express-rate-limit"
2. query-docs
libraryId: "/nfriedly/express-rate-limit"
query: "middleware setup options"
3. Implement using verified current API
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.