SKILLEMALL.ai

CF technical-project-management

Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track milestones, risks, issues, dependencies, forecasts, scope changes, and recovery. Use when a team has no project manager, a TPM needs decision-ready analysis, a project is slipping, or commitments and handoffs need coordination. Use `technical-program-management` instead when multiple related projects, teams, vendors, shared capacity, or benefits must be coordinated toward one outcome. Adapt depth to the user's expertise. Do not use for a standalone coding task, product discovery or strategy, only writing an implementation plan, only diagnosing Kanban flow, operating a ticket tool, incident command, or a release go/no-go decision; route those to specialists.

magnus919/agent-skills Agent Skills author: magnus919 MIT 36 files · 2 scripts body ≈ 2 663 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches…

As a process F 47/100 · Will not run — References files that are not bundled: ../product-discovery/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../implementation-planning/SKILL.md

AnalyzerOperations and projectsSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
F
47/100
Will not run
References files that are not bundled: ../product-discovery/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../implementation-planning/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: 26. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../product-discovery/SKILL.md
  • warning missing-ref reference to a missing file: ../product-roadmapping-and-portfolio/SKILL.md
  • warning missing-ref reference to a missing file: ../implementation-planning/SKILL.md
  • warning missing-ref reference to a missing file: ../kanban-guru/SKILL.md
  • warning missing-ref reference to a missing file: ../product-shaping/SKILL.md
  • warning missing-ref reference to a missing file: ../product-operations-and-governance/SKILL.md
  • warning missing-ref reference to a missing file: ../chief-of-staff-methodology/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: ../jira/SKILL.md
  • warning missing-ref reference to a missing file: ../linear/SKILL.md
  • warning missing-ref reference to a missing file: ../financial-modeling/SKILL.md
  • warning missing-ref reference to a missing file: ../legal-strategy/SKILL.md

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: ../product-discovery/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../implementation-planning/SKILL.md
  • 0Tools and files. 14 referenced file(s) missing: ../product-discovery/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md, ../implementation-planning/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 8 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 16 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2663 tokens
  • 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
  • +3Description length 855: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 16 items
  • +4Reference files are cited in the instructions (14 of 14)
  • +1License stated

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