kevinslin/mature
active/mature/SKILL.md
Add or update CLI maturity ratings in repo docs.
$ install --global
skillsauthnpx skillsauth add kevinslin/skills matureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 10, 2026, 7:13 AM157.9s1 file scanned
SKILL.md
- name:
- mature
- description:
- Add or update CLI maturity ratings in repo docs.
- dependencies:
- []
mature
Add a tool maturity index to README.md, label each CLI entry with a maturity emoji, and make the repo rules in AGENTS.md require maturity labels for future tools.
Workflow
- Read
README.mdandAGENTS.md. - Add or update a
## Tool maturitysection inREADME.mdbefore the CLI index using exactly:🌱 seed: just testing, might not work🪴 sprout: has seen some use, might still have hardcoded assumptions and not generalized🌳 oak: battle tested. good for general usage
- Update each CLI bullet in
README.mdto include exactly one maturity emoji before the linked tool name. - Preserve the existing README bullet format apart from the added maturity marker.
- Update
AGENTS.mdso future CLI additions must:- keep the
## Tool maturitysection present and current - include a maturity emoji/classification in each CLI index bullet
- use exactly the same
🌱 / 🪴 / 🌳definitions as the README legend
- keep the
- If the user provides tool classifications, apply them directly.
- If the user asks to add a new tool and does not provide a maturity level, ask for one or clearly note the assumption you made.
Output contract
README.mdmust contain a## Tool maturitysection before## CLI index.- Every CLI bullet in
README.mdmust start with exactly one of:🌱🪴🌳
AGENTS.mdmust instruct future agents to maintain the maturity legend and include one maturity marker per CLI entry.- Do not invent additional maturity levels unless the user explicitly asks.
Related Skills
kevinslin/slack-report
development
VerifiedTrustedCommunity
Generate incremental Slack digests for channels, topics, and categories.
9SKILL.mdUpdated May 29, 2026
kevinslin/claw-score
testing
VerifiedTrustedCommunity
Audit an OpenClaw maturity-scorecard surface into an evidence-backed component score report. Use when given a surface from an OpenClaw maturity-scorecard.md and asked to score coverage, quality, readiness, or generate a detailed surface report plus per-component subreports.
9SKILL.mdUpdated May 29, 2026
kevinslin/spec-template
tools
VerifiedTrustedCommunity
Turn an existing concrete spec into a reusable generic spec template. Use when asked to create a generic spec, template spec, reusable implementation template, or generalized version of a spec from a specific implementation such as one plugin, channel, integration, feature, or PR.
9SKILL.mdUpdated May 28, 2026
kevinslin/grok
data-ai
VerifiedTrustedCommunity
Trace how something works with an investigator subagent and a skeptical reviewer subagent.
9SKILL.mdUpdated May 28, 2026