Our review
Spawns a background agent to answer a question from primary sources (official docs, source code, specs) and records the findings, with a citation per claim, in a Markdown file inside the repo.
Strengths
- Forces primary sources over second-hand write-ups by tracing every claim back to the source that owns it.
- Requires a cited source for each claim, which keeps the resulting notes auditable.
- Delegates the work to a background agent so you can keep working while it reads.
- Asks the agent to follow the repo's existing notes convention, or to state clearly where it put the file if none exists.
Limitations
- Specifies no file structure, sections, or citation format, so output shape depends entirely on repo context.
- Quality hinges on the agent's access to primary sources; paywalled or authenticated material may be out of reach.
- No verification or review step is described after the notes are written.
Use it when you need a factual answer or API details grounded in trustworthy sources, with notes that persist in the repository.
Skip it for opinion synthesis, secondary literature reviews, or throwaway answers that should not live in the repo.
Security analysis
SafeThe skill instructs the agent to research using primary sources and write findings to a Markdown file. It does not command destructive actions, exfiltration, obfuscation, or disabling safety. No dangerous tools are declared or directly invoked, and the instructions are benign.
No concerns found
Examples
Research how the Stripe API handles rate limiting — the actual limits, response headers, and recommended retry behaviour. Cite the official docs for each claim and save the notes as Markdown where this repo keeps its research.Research whether httpx's connection pool reuses connections across redirects. Check the source code and the official docs, not blog posts, and write up the findings with citations in a Markdown file.Research what the OAuth 2.1 draft actually says about refresh token rotation, going back to the spec text itself. Save a cited Markdown summary following this repo's existing notes convention.name: research description: 'Investigate a question against high-trust primary sources and capture findings as Markdown in the repo. Use to research a topic or gather docs/API facts.'
Spin up a background agent to do the research, so you keep working while it reads.
Its job:
- Investigate the question against primary sources — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it.
- Write the findings to a single Markdown file, citing each claim's source.
- Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Review Existing Content
Documentation
Reviews documentation pages selected by the daily content-review workflow, applying high-confidence fixes and opening auditable pull requests. For the review-existing-content pipeline.