.agents/skills/ai-readiness/SKILL.md
# AI Readiness Skill — AuditKit This skill is auto-included in the generated ZIP when the AI Readiness pillar score is below 90. AI Readiness measures how discoverable and usable your project is by AI coding agents, LLM crawlers, and vibe-coders who ask their AI about your tool. --- ## llms.txt The `llms.txt` standard (https://llmstxt.org) is a Markdown file at your domain root that gives LLMs context about your project — like `robots.txt` but for AI. ``` # YourProject > One-sentence desc
npx skillsauth add nirholas/auditkit .agents/skills/ai-readinessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill is auto-included in the generated ZIP when the AI Readiness pillar score is below 90.
AI Readiness measures how discoverable and usable your project is by AI coding agents, LLM crawlers, and vibe-coders who ask their AI about your tool.
The llms.txt standard (https://llmstxt.org) is a Markdown file at your domain root that gives LLMs context about your project — like robots.txt but for AI.
# YourProject
> One-sentence description of what your project does.
## Links
- Docs: https://yourdomain.com/docs
- Repo: https://github.com/you/project
## What it does
Brief description of capabilities, use cases, and how to get started.
## Quick Start
Installation and basic usage in 5 lines.
## License
MIT
Place at: https://yourdomain.com/llms.txt
For Next.js, create public/llms.txt.
A longer version with complete API docs, type signatures, examples, and architecture context. Aimed at giving an LLM full context to work with your codebase without needing to read source files.
Place at: https://yourdomain.com/llms-full.txt
Instructions for AI coding agents working in your repository. Should include:
# AGENTS.md
## Project
Brief description.
## Tech Stack
- Framework, language, package manager
## Directory Map
Key directories and what they contain.
## Commands
\`\`\`bash
npm run dev
npm run build
npm run test
\`\`\`
## Conventions
- Code style preferences
- Patterns to follow
- Things to avoid
Same concept as AGENTS.md but with system-specific context:
CLAUDE.md — Claude-specific notes (multi-file editing patterns, tool use preferences)GEMINI.md — Gemini-specific notes (context window usage, grounding)Allow AI crawlers explicitly so they index your content for training and search:
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: Google-Extended
Allow: /
User-agent: anthropic-ai
Allow: /
User-agent: PerplexityBot
Allow: /
# Block specific paths from all bots
User-agent: *
Disallow: /private/
Allow: /
For GitHub repos, AI Readiness also checks:
| File | Why it matters |
|------|----------------|
| README.md | First thing an LLM reads about your project |
| CONTRIBUTING.md | AI agents follow contribution guidelines |
| AGENTS.md | Explicit AI agent instructions |
| CLAUDE.md | Claude-specific context |
| GEMINI.md | Gemini-specific context |
| .github/copilot-instructions.md | GitHub Copilot context |
| llms.txt | LLM-friendly project summary |
| LICENSE | Needed for AI training dataset classification |
| GitHub Topics | Makes repo discoverable in AI-powered search |
Structured data helps AI systems understand what your page is about:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "YourApp",
"description": "What it does",
"url": "https://yourdomain.com",
"applicationCategory": "DeveloperApplication",
"operatingSystem": "Web",
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "USD"
}
}
</script>
development
# Structured Data Skill — AuditKit This skill is auto-included in the generated ZIP when the Structured Data pillar score is below 90. Structured data (Schema.org JSON-LD) helps search engines and AI systems understand your content type — enabling rich results in Google Search and better AI discoverability. --- ## JSON-LD Basics Always use `application/ld+json` script tags in `<head>`. Never use Microdata or RDFa (JSON-LD is the recommended format per Google). ```html <script type="applica
development
# SEO Skill — AuditKit This skill is auto-included in the generated ZIP when the SEO pillar score is below 90. ## Critical Requirements Every page MUST have: - `<title>` tag (50–60 characters) - `<meta name="description">` (120–158 characters) - `<link rel="canonical">` pointing to the preferred URL - At least one `<h1>` tag ## Meta Tags Checklist ```html <head> <!-- Required --> <title>Page Title — Site Name</title> <meta name="description" content="120–158 char description of this s
development
# Security Skill — AuditKit This skill is auto-included in the generated ZIP when the Security pillar score is below 90. ## HTTP Security Headers Add all of these to every response. Vercel users: add to `vercel.json`. Next.js users: add to `next.config.ts`. ### next.config.ts ```typescript const securityHeaders = [ { key: 'Strict-Transport-Security', value: 'max-age=63072000; includeSubDomains; preload', }, { key: 'Content-Security-Policy', value: [ "default-src
development
# Performance Skill — AuditKit This skill is auto-included in the generated ZIP when the Performance pillar score is below 90. ## What it covers Core Web Vitals (LCP, CLS, TBT/FID, FCP, TTFB, Speed Index) and general page weight / render-blocking resource issues. ## Thresholds (Google's "good" targets) | Metric | Good | Needs Improvement | Poor | |--------|------|-------------------|------| | LCP (Largest Contentful Paint) | < 2.5s | 2.5–4s | > 4s | | CLS (Cumulative Layout Shift) | < 0.1 |