assess-readiness
Skill0 starsChanged 40 days agoLicence not identifiedView on GitHub
Assess the readiness level of an Escape Velocity technology or of an approach to a gap on its scale (TRL, MRL, clinical drug or clinical device phases), with evidence for the level. Use when a technology moves to mapped, when new evidence suggests a higher or lower level, or when a pull request changes a readiness value.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-evidence-from-doiSkill
- cross-domain-transferSkill
- decompose-technologySkill
- define-technologySkill
- find-neglected-gapsSkill
- first-contributionSkill
- review-evidenceSkill
- scout-literatureSkill
- translate-pageSkill
- weekly-briefSkill
- write-impactSkill
The file
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.