OUR STANDARDS
Useful beats
impressive-looking.
A small directory with clear evidence is more useful than a large list of unsupported promises. We help you choose a resource and understand what you still need to check.
Independent, by design
Claude Duet Guide is an independent editorial project. It is not an Anthropic product, official marketplace or support channel. Product names identify the tools being discussed; all trademarks belong to their owners.
We do not sell access to Claude Duet. Use the official website for account access, billing, support and the research-preview waitlist. This site has no account signup, paid placement or affiliate links.
What earns a listing
- A reachable primary source: an official product announcement, repository or help page.
- A specific task that a reader can understand without decoding marketing language.
- A visible type and platform-compatibility label.
- A practical limitation and a suggested low-risk evaluation task.
The initial selection covers document work, analysis, design, sales and operations. It is a curated starting set, not an exhaustive index or a popularity ranking. Resource counts come from the actual published entries: currently 22.
What we verified—and what we did not
On , we reviewed the official Duet announcement, Anthropic's skills repository, the knowledge-work plugins repository and the unified-directory help page. Each entry links to its original source and carries the review date.
We verified documentation, not execution inside Duet. We have not installed these resources in a Duet account, measured time saved or tested every external service. We do not publish fabricated downloads, install totals, star ratings, reviews or success rates. The data model rejects fields that look like popularity or revenue metrics, so none can be added by accident.
Suggested prompts are original editorial examples, not vendor claims or recorded test results. Repository pages can change after our review; inspect the linked source before use.
How is each label proven?
Every entry stores one sentence quoted word for word from a saved copy of its source, plus the copy’s retrieval date and SHA-256 hash. A build check fails if the sentence is missing.
“Duet documented” is only allowed when that sentence comes from the Claude Duet announcement. Other facts shown on an entry page, such as plugin commands or skill sections, are checked against the saved copy the same way. The saved copies and their hashes are in the project’s research folder; the announcement copy was retrieved on . The same data is published as catalog.json, and a plain-text index for AI tools is at llms.txt.
How are the articles reviewed?
The workflow articles are documentation reviews. They list every source with its retrieval date, label each claim by the kind of source behind it, and say plainly when Claude Duet support is not documented.
A separate publication manifest decides which drafts are live and records the exact text that was approved, so an edited draft cannot reach the site unnoticed. The build refuses a source that was not retrieved, and checks that each longer quotation exists in the stored copy of a source the article lists. No article reports a hands-on test, and its sample prompts are illustrations, not observed output.
Primary sources
- Introducing Claude Duet — product scope, named integrations, approval rules and preview limits.
- Anthropic Agent Skills — skill files, usage context and license caveats.
- Anthropic knowledge-work plugins — job-specific bundles and documented environments.
- Unified skills, connectors and plugins directory — official account-level discovery instructions.
Design inspiration
The copy-and-run prompt pattern and category browsing were inspired by the Grokbot skills library, and the dense, scannable list layout by the startup directory at TrustMRR, whose cards each link to one profile page. We borrowed layout ideas only. We do not show revenue, rankings, installs or ratings, and neither site endorses this one.
Maintenance and corrections
Compatibility should change only when new evidence supports it. A documentation update can change a label; a hands-on test needs its own dated account of environment, task, result and limitations. A cosmetic edit does not refresh the evidence date.
If an entry is unclear, use its original source to verify the claim before taking action. We do not currently accept public submissions or collect contact details through this site.
Privacy
Search, filters and sorting run locally in your browser, and your choices live only in the page address so you can share a view. This site has no advertising pixels, no analytics script, no newsletter form, no cookies and no application database. We have not chosen an analytics provider, so none is installed. Fonts and scripts are served from this site, and the copy buttons use your browser’s clipboard only when you press them. Our hosting provider may process ordinary request logs to deliver and protect the site. Following an external link takes you to that provider's privacy policy.