Agent skill
opensrc-inspect
Fetch, inspect, and manage local opensrc source snapshots for packages and GitHub repositories. Use when you need dependency or upstream repo source code locally for deeper implementation review, API edge-case analysis, or version-aligned source inspection. Do not use as a general web-research skill.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/opensrc-inspect
SKILL.md
Opensrc Inspect
Use this skill when source-level dependency inspection is materially useful and API docs alone are not enough.
Workflow
- Read the repo
AGENTS.md. - Check existing snapshots first:
opensrc listcat opensrc/sources.jsonwhen present
- Prefer safe fetches that avoid repo mutation:
opensrc <package> --modify=falseopensrc pypi:<package> --modify=falseopensrc crates:<package> --modify=falseopensrc <owner>/<repo> --modify=false
- Inspect the fetched source path and cite exact files and versions when using it in analysis.
- Refresh snapshots after meaningful dependency upgrades if internals changed.
Use When
- You need to inspect a package implementation, not just its docs or types.
- You need source-level evidence for a migration, bug, or compatibility question.
Do Not Use When
- Official docs, types, or direct code inspection already answer the question.
- The task is broad web research or release-note discovery.
Guardrails
- Default to
--modify=false. - Treat
opensrc/as read-only source context. - Use Context7, Exa, or
web.runfor official/latest docs and changelogs; use opensrc only for implementation internals.
Outputs
- fetched source target and version summary
- exact local paths used for analysis
- concise recommendation on whether deeper source inspection changed the conclusion
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?