pm-ai-skills-framework
AGENTS.md0 starsChanged 44 days agoMITView on GitHub
Instructions for any coding agent working in this repository: Claude Code, GitHub Copilot, and Codex all read this file. CLAUDE.md imports it and .github/copilot-instructions.md points to it; keep the rules here. A governance layer over NVIDIA SkillEvaluator, exercised on twelve portfolio-management skills. Start with README.md; docs/README.md indexes every document by goal, and docs/10_DEVELOPMENT_ROADMAP_AND_PROGRESS.md is the current status. - Public and synthetic data only. Skills read the local fixtures in synthetic_data_pipeline/. No real portfolio data, internal system names, or credentials in…
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- skillevaluator-masterySkill
- skillevaluator-masterySkill
- benchmark-comparisonSkill
- concentration-analysisSkill
- exposure-analysisSkill
- liquidity-analysisSkill
- m1-tier3-smokeSkill
- market-move-explanationSkill
- performance-attributionSkill
- pm-commentary-generationSkill
- portfolio-change-analysisSkill
- portfolio-overviewSkill
- position-investigationSkill
- risk-explanationSkill
- scenario-analysisSkill
- skillevaluator-masterySkill
The file
Files
AGENTS.md
Instructions for any coding agent working in this repository: Claude Code,
GitHub Copilot, and Codex all read this file. CLAUDE.md imports it and
.github/copilot-instructions.md points to it; keep the rules here.
What this repository is
A governance layer over NVIDIA SkillEvaluator, exercised on twelve
portfolio-management skills. Start with README.md; docs/README.md indexes
every document by goal, and docs/10_DEVELOPMENT_ROADMAP_AND_PROGRESS.md is
the current status.
Commands
uv sync --extra dev # install, including dev tools
uv run pytest -q # all tests; no network
uv run ruff check . && uv run ruff format --check . --exclude "*.md"
uv run pmai-skills validate skills # offline framework checks
uv run python scripts/build_curriculum_pages.py # course site, into public/Rules
- Public and synthetic data only. Skills read the local fixtures in
synthetic_data_pipeline/. No real portfolio data, internal system names, or credentials in code, docs, commits, or evaluation cases. - No network in tests. Nothing under
tests/may call a model, an embedding provider, or any other service. - Live evaluation costs money; never start it unasked. Tier 2 needs an
embedding key, and a full Tier 3 run cost $15-45 per skill. Run Tier 1 and
the offline checks freely; run
pmai-skills similarity,pmai-skills evaluate, orskillevaluator ... --agent-evalonly when a person has asked for that specific run and its cost. - Do not commit raw reports.
reports/is git-ignored. Tracked evidence is each skill'sBENCHMARK.mdandBENCHMARK.json; do not link docs to files underreports/(tests/test_docs_links.pyfails if you do). - Only
framework/adapters/reads NVIDIA's raw report format. Everything downstream uses the normalized schema, so an evaluator upgrade stays contained. - The evaluator is pinned to one commit, installed by
.github/workflows/skills-quality.ymlanddocs/MILESTONE_1_SETUP.md, and changed only underdocs/13_NVIDIA_EVALUATOR_UPGRADE_POLICY.md. - Edit the canonical skill, not its loaders. Skills live in
skills/<name>/..claude/skills/and.agents/skills/hold identical thin loaders that point back to it;tests/test_skill_loaders.pykeeps them in step. - Every skill needs an owner. CI fails on the
domain-owner-requiredplaceholder. - The course site is generated. Edit the skill's
references/, docs 15 and 16, orsite/; never editpublic/. Quiz questions are insite/quizzes.yaml, and every answer must be stated in its module. ruff formatrewrites Python inside Markdown fences, which is why CI excludes*.md. Do not reformat docs as a side effect of a code change.
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.

