package-registry-ti
Skill2 starsChanged 34 days agoMITView on GitHub
Discovers npm/PyPI Technology Intelligence candidates via file fixtures or live registry (Captain-gated)
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-core-operating-model.mdcCursor rule
- .cursor/rules/01-plan-approval-gate.mdcCursor rule
- .cursor/rules/02-git-worktree-policy.mdcCursor rule
- .cursor/rules/03-validation-definition-of-done.mdcCursor rule
- .cursor/rules/04-documentation-memory.mdcCursor rule
- accessibility-reviewSkill
- agent-skills-packagingSkill
- autonomy-budgetSkill
- bounded-autonomySkill
- candidate-promotionSkill
- capability-planningSkill
- code-reviewerSkill
- code-structure-cleanupSkill
- compass-evaluatorSkill
- context-inodesSkill
- dependency-supply-chainSkill
- docker-cloudSkill
- embedding-providersSkill
- execution-telemetrySkill
- experience-routingSkill
- experience-skill-trainingSkill
- external-knowledge-ingestSkill
- github-integrationSkill
- goose-agent-orchestrationSkill
- harness-gcSkill
- hosted-vector-dbSkill
- implementation-planningSkill
- ios-engineeringSkill
- knowledge-stewardSkill
- linear-integrationSkill
- node-engineeringSkill
- northstar-connected-routineSkill
- notion-integrationSkill
- persistent-role-promotionSkill
- playwright-browser-validationSkill
- postgres-prismaSkill
- procedure-playbooksSkill
- project-overseerSkill
- pull-request-preparationSkill
- python-mlSkill
- react-engineeringSkill
- repository-discoverySkill
- review-fix-loopSkill
- security-audit-proceduresSkill
- security-reviewSkill
- skill-learning-loopSkill
- skill-lifecycleSkill
- source-code-contextSkill
- technology-intelligence-liveSkill
- testing-validationSkill
- worktree-orchestrationSkill
The file
Files
Package Registry Technology Intelligence
Use this Skill when
The Captain wants package-registry discovery signals (npm / PyPI) in capability plans — offline fixtures or opt-in live registry queries.
Inputs
- Offline fixtures (
COMPASS_TI_PROVIDER=package-registry-file) or - Live registries (
COMPASS_TI_PROVIDER=package-registry) — Captain local only - Optional
COMPASS_PACKAGE_TI_ECOSYSTEMS=npm,pypi(default both) - Optional
COMPASS_PACKAGE_TI_FIXTURES_DIRfor file mode
Procedure
Offline fixtures (CI-safe):
COMPASS_TI_PROVIDER=package-registry-file \ ./scripts/query-technology-intelligence.sh --query "schema validation typescript"Live npm + PyPI (Captain local; never CI default):
COMPASS_TI_PROVIDER=package-registry \ ./scripts/query-technology-intelligence.sh --query "schema validation"- Candidates appear only under Technology Intelligence Candidates
(
NOT APPROVED FOR EXECUTION). Promote viacandidate-promotion/skill-lifecycle— never auto-install.
Output
CandidateCapabilitylist withapproved_for_execution: false
Prohibited actions
- Live registry network calls in CI or as default provider
- Setting
approved_for_execution: true - Auto-installing packages or Skills from TI results
- Treating package candidates as approved Compass capabilities
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.