SKILLEMALL.ai
GitHub ↗ RU Sign in

BF technical-program-management

Manage technical programs made of multiple related projects, products, teams, or vendors: establish the program mandate and benefits, align component work, manage cross-project dependencies and shared capacity, govern risks and decisions, coordinate transformation and adoption, and communicate program health to executives, delivery teams, and partners. Use when the work is a coordinated change larger than one project or when component projects are locally green but the combined outcome is at risk. Do not use for single-project control, detailed implementation planning, product portfolio or capital-allocation decisions, enterprise architecture design, release approval, or live incident command; route those to the named specialists.

magnus919/agent-skills Agent Skills author: magnus919 MIT 13 files body ≈ 3 207 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Manage technical programs made of multiple related projects, products, teams, or vendors: establish the program mandate and benefits, align component work…

As a process F 55/100 · Will not run — References files that are not bundled: ../technical-project-management/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../strategy-frameworks/SKILL.md

GeneratorInfrastructureData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: ../technical-project-management/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../strategy-frameworks/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../technical-project-management/SKILL.md
  • warning missing-ref reference to a missing file: ../product-roadmapping-and-portfolio/SKILL.md
  • warning missing-ref reference to a missing file: ../strategy-frameworks/SKILL.md
  • warning missing-ref reference to a missing file: ../product-operations-and-governance/SKILL.md
  • warning missing-ref reference to a missing file: ../enterprise-architecture/SKILL.md
  • warning missing-ref reference to a missing file: ../implementation-planning/SKILL.md
  • warning missing-ref reference to a missing file: ../org-design/SKILL.md
  • warning missing-ref reference to a missing file: ../technology-radar/SKILL.md
  • warning missing-ref reference to a missing file: ../release-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../production-readiness/SKILL.md
  • warning missing-ref reference to a missing file: ../site-reliability-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../product-adoption/SKILL.md
  • warning missing-ref reference to a missing file: ../product-lifecycle-learning/SKILL.md

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: ../technical-project-management/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../strategy-frameworks/SKILL.md
  • 0Tools and files. 13 referenced file(s) missing: ../technical-project-management/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../strategy-frameworks/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 31 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3207 tokens
  • low 10 top-level sections: this looks like several domains in one skill
  • medium 14 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4No input/output examples
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 740: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 31 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (5 of 5)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.