verify Skill
Drive the contracts engine's runtime surface (the stdio MCP server) to verify changes end-to-end. Scoped to public-plugins/plugins/healthcare/skills/contracts/ and ../../servers/documents/. Published by anthropics in healthcare.
Decision snapshot
Is this a fit?
Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
12 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is verify Skill?
Drive the contracts engine's runtime surface (the stdio MCP server) to verify changes end-to-end. Scoped to public-plugins/plugins/healthcare/skills/contracts/ and ../../servers/documents/. Published by anthropics in healthcare. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Declared skill metadata
- Source file: plugins/healthcare/skills/contracts/.claude/skills/verify/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use verify Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/healthcare
- Skill file: plugins/healthcare/skills/contracts/.claude/skills/verify/SKILL.md
What it does
Drive the contracts engine's runtime surface (the stdio MCP server) to verify changes end-to-end. Scoped to public-plugins/plugins/healthcare/skills/contracts/ and ../../servers/documents/.
Skill instructions
Verifying contracts-engine changes The engine is the MCP server at ../../servers/documents/src/index.mjs — plain runnable .mjs, no build step; the source IS the shipped artifact. Most changes are drivable without a full /contracts session by speaking JSON-RPC to the server over stdio. - Typecheck: cd ../../servers/documents && bun run check (tsc over the .mjs via checkJs). There is no bundle; edits to src are live immediately. - Data: ~/.claude/data/healthcare/documents/data.sqlite — the dir is the server's name (documents), not the skill's (contracts); shared across checkouts; safe to delete — schema v-check tells users to do the same. For throwaway runs point CLAUDEHEALTHCAREDATA at a scratch PARENT dir (the server appends documents/) — never drive tests against the live db. Corpus names live in corpusdocuments.corpus; query before assuming. - CLI mode: node ../../servers/documents/src/index.mjs <tool '<json-args' runs one tool call without MCP — result JSON on stdout, exit 1 + stder
Verified compatibility and discovery
Frequently asked questions
What is verify?
verify is a open-source AI agent skill with Copy skill directory. Drive the contracts engine's runtime surface (the stdio MCP server) to verify changes end-to-end. Scoped to public-plugins/plugins/healthcare/skills/contracts/ and ../../servers/documents/.
Who is verify best for?
verify is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install verify?
Install or run verify using Copy skill directory. Check verify for the latest setup command.
Is verify actively maintained?
verify may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
