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
- ViksyaHQ/ai-readiness-assessmenttheir own version, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ViksyaHQ/ai-readiness-assessment★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository229 other files it gives its agents.
- accessibility-auditorSkill
- agent-armySkill
- agent-eval-harnessSkill
- agent-swarm-deployerSkill
- agent-team-builderSkill
- agent-to-agentSkill
- ai-coding-guardrailsSkill
- animateSkill
- api-documentation-writerSkill
- api-endpoint-scaffolderSkill
- api-load-testerSkill
- athlete-social-media-managerSkill
- before-you-buildSkill
- bi-measure-builderSkill
- board-deck-generatorSkill
- bookkeeping-closeSkill
- bracket-predictorSkill
- brand-consistency-checkerSkill
- brand-voice-analyzerSkill
- browser-test-loopSkill
- budget-optimizerSkill
- cash-flow-forecasterSkill
- champion-identifierSkill
- churn-autopsySkill
- claude-design-criticSkill
- claude-design-system-architectSkill
- claude-landing-composerSkill
- claude-md-writerSkill
- client-health-dashboardSkill
- client-proposal-generatorSkill
- code-review-proSkill
- cold-email-sequence-generatorSkill
- color-palette-extractorSkill
- commercial-lease-analyzerSkill
- company-announcement-writerSkill
- competitor-content-analyzerSkill
- competitor-intel-agentSkill
- competitor-price-trackerSkill
- compliance-checkerSkill
- contact-hunterSkill
- content-repurposerSkill
- context-budgetSkill
- contract-analyzerSkill
- contract-redlinerSkill
- conversation-archaeologistSkill
- cowork-calendar-defragSkill
- cowork-contract-renewal-radarSkill
- cowork-data-room-builderSkill
- cowork-deal-roomSkill
- cowork-expense-auditSkill
- cowork-folder-organizerSkill
- cowork-hiring-screenerSkill
- cowork-home-inventorySkill
- cowork-inbox-triageSkill
- cowork-invoice-chaserSkill
- cowork-medical-bill-auditorSkill
- cowork-qbr-builderSkill
- cowork-rfp-responseSkill
- cowork-sop-writerSkill
- cowork-tax-prep-organizerSkill
- The first 60 shown.
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
- Distinctive: line 23
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 …
- Distinctive: line 42
Never inflate scores. A business that scores 2.0 needs to hear that honestly.
- Distinctive: line 43
Always provide evidence. Back every score with specific observations, not assumptions.
- Distinctive: line 46
Use no jargon without explanation.
- Distinctive: line 48
Consider the full cost. Include ongoing costs (maintenance, retraining, monitoring), not just implementation.
- Distinctive: line 51
Use no emojis. Keep all output professional and text-based.
≈ “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.
Files
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.
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.

