Ai readiness assessment
Skill bg-szy/TOP-SKILLS/skills/claude-skills/ai-readiness-assessment
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.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill ai-readiness-assessmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.6 KB, 690 tokens by cl100k_base, as published. Nobody here has run it
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 completeai-readiness-report.mdstructure to fill in.
Workflow
- Gather context. Collect information through conversation, document review, and codebase analysis. See
references/methodology.md(Phase 1) for channels and the question set inreferences/dimensions.md. - 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. - Calculate the overall score. Apply the weighted formula and map it to a readiness level using the table in
references/methodology.md(Phase 2). - 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).
- Build recommendations. Produce prioritized actions across the five OneWave priority tiers, tailoring for company size and industry (Phase 4 and tailoring section).
- Generate the report. Write
ai-readiness-report.mdfollowingreferences/output-template.md, then highlight the top 3 immediate actions.
The Six Dimensions
| Dimension | Weight |
|---|---|
| Data Maturity | 25% |
| Technology Stack | 20% |
| Team Skills and Capacity | 20% |
| Process Documentation | 15% |
| Budget and Resources | 10% |
| Organizational Culture | 10% |
See references/dimensions.md for the full rubric and questions.
Core Rules
- Never inflate scores. A business that scores 2.0 needs to hear that honestly; false optimism wastes money and time.
- Always provide evidence. Back every score with specific observations, not assumptions.
- Be actionable. Pair every identified gap with a concrete recommendation.
- Respect budget realities. Include cost-appropriate options; not every organization needs enterprise-grade solutions.
- Use no jargon without explanation. The report is read by business leaders, not only technologists.
- Flag deal-breakers. When a dimension scores 1.0, state explicitly that AI initiatives should not begin until it is addressed.
- Consider the full cost. Include ongoing costs (maintenance, retraining, monitoring), not just implementation.
- Recommend the right AI. Match recommendations to actual readiness; do not recommend deep learning to a company that has not consolidated its data.
- Maintain OneWave AI alignment. Frame all recommendations within pragmatic, ROI-driven AI adoption. Avoid hype; focus on business value.
- Use no emojis. Keep all output professional and text-based.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in 690 tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07
- Announce the skill at startin 54 of 1637, across 26 files
- Convert legacy doc files before editingin 45 of 1637, across 7 files
- Predict questions readers might askin 42 of 1637, across 4 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test the document with a fresh context-less instancein 42 of 1637, across 3 files
- Include exact file paths in every taskin 42 of 1637, across 15 files
- Ask interview questions one at a timein 42 of 1637, across 27 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 2 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.