agentleFS
OneWave-AIOneWave-AI/claude-skills/ai-readiness-assessment/SKILL.md

ai-readiness-assessment

Skill378 starsChanged 53 days agoMITView on GitHub

Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the gap analysis. For each dimension below 4.0, document current state, target state, the gap, its impact, and the effort to close it …

    line 23
  2. Distinctive:

    Never inflate scores. A business that scores 2.0 needs to hear that honestly.

    line 42
  3. Distinctive:

    Always provide evidence. Back every score with specific observations, not assumptions.

    line 43
  4. Distinctive:

    Use no jargon without explanation.

    line 46
  5. Distinctive:

    Consider the full cost. Include ongoing costs (maintenance, retraining, monitoring), not just implementation.

    line 48
  6. Distinctive:

    Use no emojis. Keep all output professional and text-based.

    line 51

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI Readiness Assessment Skill

Conduct a structured, evidence-based evaluation of a business's readiness for AI adoption across six dimensions, then produce a detailed ai-readiness-report.md covering scores, gap analysis, and prioritized next steps. Aligned with OneWave AI's pragmatic, ROI-driven audit methodology.

Contents

  • references/dimensions.md — The six dimensions, full 1-5 scoring rubric, and key questions per dimension.
  • references/methodology.md — Information-gathering, scoring math and interpretation table, gap analysis, recommendation priorities, company-size and industry tailoring, and conversation flow.
  • references/output-template.md — The complete ai-readiness-report.md structure to fill in.

Workflow

  1. Gather context. Collect information through conversation, document review, and codebase analysis. See references/methodology.md (Phase 1) for channels and the question set in references/dimensions.md.
  2. Score the six dimensions. Rate each from 1 to 5 against the rubric in references/dimensions.md. Be honest and conservative, use half-points for nuance, and record the evidence behind every score.
  3. Calculate the overall score. Apply the weighted formula and map it to a readiness level using the table in references/methodology.md (Phase 2).
  4. Run the gap analysis. For each dimension below 4.0, document current state, target state, the gap, its impact, and the effort to close it (Phase 3).
  5. Build recommendations. Produce prioritized actions across the five OneWave priority tiers, tailoring for company size and industry (Phase 4 and tailoring section).
  6. Generate the report. Write ai-readiness-report.md following references/output-template.md, then highlight the top 3 immediate actions.

The Six Dimensions

DimensionWeight
Data Maturity25%
Technology Stack20%
Team Skills and Capacity20%
Process Documentation15%
Budget and Resources10%
Organizational Culture10%

See references/dimensions.md for the full rubric and questions.

Core Rules

  1. Never inflate scores. A business that scores 2.0 needs to hear that honestly; false optimism wastes money and time.
  2. Always provide evidence. Back every score with specific observations, not assumptions.
  3. Be actionable. Pair every identified gap with a concrete recommendation.
  4. Respect budget realities. Include cost-appropriate options; not every organization needs enterprise-grade solutions.
  5. Use no jargon without explanation. The report is read by business leaders, not only technologists.
  6. Flag deal-breakers. When a dimension scores 1.0, state explicitly that AI initiatives should not begin until it is addressed.
  7. Consider the full cost. Include ongoing costs (maintenance, retraining, monitoring), not just implementation.
  8. Recommend the right AI. Match recommendations to actual readiness; do not recommend deep learning to a company that has not consolidated its data.
  9. Maintain OneWave AI alignment. Frame all recommendations within pragmatic, ROI-driven AI adoption. Avoid hype; focus on business value.
  10. Use no emojis. Keep all output professional and text-based.

Download now (ZIP)

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.