agentleFS
anyreachaianyreachai/claude-skills/skills/maturity-assessment/SKILL.md

maturity-assessment

Skill1 starsChanged 7 months agoNo licenceView on GitHub

Generate an operational maturity assessment dashboard (.jsx) that benchmarks Anyreach's enterprise readiness across key domains, combining quantitative metrics with qualitative analysis. Use this skill whenever Richard asks to assess, benchmark, audit, or score Anyreach's operational maturity, enterprise readiness, process maturity, or SOP coverage. Also trigger on phrases like "how are we doing operationally", "are we enterprise-ready", "grade our processes", "how mature are our ops", "pound for pound assessment", "maturity dashboard", "benchmark our SOPs", "how do we stack up", or any request to evaluate Anyreach's operational sophistication relative to funding stage. Trigger even for partial requests like "score our contract process" or "how's our compliance posture" since the full cross-domain assessment produces the most useful output. This skill should also trigger when Richard uploads SOP documents and asks for an assessment or analysis of operational readiness.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.