maturity-diagnosis
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Assess current readiness of candidates using TRL 9-level, NASSS 7-dimension, and Innovation Readiness Level frameworks.
In this repository119 other files it gives its agents.
- adaptive-pair-selectionSkill
- adversarial-debate-protocolSkill
- advocate-constructionSkill
- aggregation-methodSkill
- alternative-scoringSkill
- appropriateness-boundingSkill
- argument-crystallizationSkill
- argument-extractionSkill
- assumption-challengeSkill
- assumption-excavationSkill
- assumption-extractionSkill
- ballot-collectionSkill
- best-option-selectionSkill
- bottleneck-identificationSkill
- category-sortingSkill
- cluster-analysisSkill
- coherence-diagnosisSkill
- collective-adjudicationSkill
- comparative-feasibility-rankingSkill
- comparison-executorSkill
- conclusion-sensitivitySkill
- conjunctive-filterSkill
- consensus-classificationSkill
- consensus-measurementSkill
- consensus-synthesisSkill
- consistency-audit-loopSkill
- constraint-classificationSkill
- constraint-drillingSkill
- constraint-identificationSkill
- constraint-identification-sopSkill
- convergence-checkSkill
- convergence-distillationSkill
- counter-thesis-constructionSkill
- coverage-scoringSkill
- criteria-interrogationSkill
- criterion-definitionSkill
- critic-attackSkill
- cycle-detectionSkill
- deliberative-calibrationSkill
- dimension-assessmentSkill
- disagreement-cartographySkill
- disagreement-mappingSkill
- disagreement-visualizationSkill
- diversity-maximizationSkill
- dominance-checkSkill
- dynamic-trackingSkill
- efficient-explorationSkill
- feasibility-assessmentSkill
- feasibility-synthesisSkill
- feedback-distributionSkill
- full-rankingSkill
- futures-calibrationSkill
- gate-criteria-definitionSkill
- gate-judgmentSkill
- inconsistency-localizationSkill
- iterative-convergence-roundSkill
- judge-verdictSkill
- judgment-collectionSkill
- maturation-pathway-designSkill
- method-sensitivity-reportSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 53
Run bottleneck-identification on the radar data to surface limiting factors
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Maturity Diagnosis
Purpose: Determine how ready a candidate is for implementation by scoring it against established maturity frameworks. Produces a multi-dimensional readiness profile that reveals which aspects are mature and which need development.
When to use:
- A candidate has been selected and needs readiness assessment before resource commitment
- Stakeholders need evidence-based maturity scores to inform go/no-go decisions
- You need to identify which dimensions are lagging and require focused maturation effort
Budget
| Metric | Target |
| Dimensions scored | >= 5 |
| Evidence items per dimension | >= 2 |
| Bottlenecks identified | >= 1 |
State Ledger
| Key | Type | Description |
| candidate | object | The candidate under assessment |
| dimensions[] | array | Dimensions being assessed |
| scores{} | map | Dimension -> score mapping |
| radar_data | object | Synthesized radar chart data |
| bottlenecks[] | array | Identified bottleneck dimensions |
Available Tactics
| Tactic | When |
| multi-dimensional-readiness-scan | Default — full readiness assessment across all dimensions |
Available SOPs
| SOP | Purpose |
| dimension-assessment | Score a single dimension |
| radar-synthesis | Combine scores into radar |
| bottleneck-identification | Find limiting dimensions |
Execution Guidance
- Identify relevant dimensions for the candidate (minimum: technical, market, regulatory, resource, organizational)
- Deploy
dimension-assessmentfor each dimension — can run in parallel - Feed all scores to
radar-synthesisto produce the composite view - Run
bottleneck-identificationon the radar data to surface limiting factors - Record all findings in state ledger
Output Format
maturity_diagnosis:
candidate: <name>
overall_readiness: <1-9 TRL scale>
dimension_scores:
technical: {score: N, evidence: [...], gaps: [...]}
market: {score: N, evidence: [...], gaps: [...]}
regulatory: {score: N, evidence: [...], gaps: [...]}
resource: {score: N, evidence: [...], gaps: [...]}
organizational: {score: N, evidence: [...], gaps: [...]}
bottlenecks: [{dimension, severity, reason}]
radar_summary: <text>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.

