Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    agent readiness audit

    1

    Audit your repository for AI agent compatibility and generate prioritized fixes to improve coding assistant performance.

    Free

    Security scanned
    agent readiness audit

    agent readiness audit

    Example session with this skill installed

    Audit this repo for agent-readiness and generate an AGENTS.md starter if needed.

    • Read your context and instructions
    • Compiled the agent readiness audit

    I have audited the repository and identified critical gaps in agent orientation and the verification loop. While the project structure is clean, the lack of explicit command mappings and large file sizes are causing agent friction.

    Agent Readiness Report — frontend-service — 55/100

    DimensionScoreMaxKey evidence
    Instructions025No .cursorrules or CLAUDE.md found in root.
    Verify loop1020package.json has scripts, but npm test fails due to missing env.
    Orientation1515Excellent README.md with clear architecture diagrams.
    Navigability10154 files exceed 800 lines (e.g., ApiClient.ts).
    Tests151592% coverage on critical paths via Jest.
    Guardrails510GitHub Actions present, but no branch protection.

    Top issues (impact × effort)

    Missing Instruction Files — Agents are guessing style and commands. Create CLAUDE.md with the discovered scripts below. Effort: S.
    2.

    Brittle Test Environment — npm test requires a local Redis instance not mentioned in docs, causing agent loops. Effort: M.

    Quick wins (≤30 min each)

    • Add a .cursorrules file to ignore the dist/ and build/ directories to save context.
    • Split ApiClient.ts into smaller service modules to stay under 500-line limits.

    AGENTS.md starter

    
    # Agent Instructions
    ## Build & Test
    - Build: `npm run build`
    - Test: `npm test`
    - Lint: `npm run lint`
    
    ## Project Structure
    - `/src/components`: UI components (React/Tailwind)
    - `/src/services`: API logic
    - `/tests`: Integration and unit tests
    
    ## Standards
    - Use TypeScript strict mode.
    - Follow functional patterns; avoid classes where possible.
    

    Next steps

    1. Commit the AGENTS.md starter to the root directory.
    2. Refactor ApiClient.ts to improve navigability scores.
    No .cursorrules or CLAUDE.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When AI coding assistants or agents struggle to navigate your codebase, fail to run tests, or hallucinate architecture patterns, the project lacks agent-readiness. This skill audits your repository to diagnose exactly why agents are underperforming. It evaluates the project across six technical dimensions to produce a prioritized improvement plan.

    What it does

    • Instruction Audit checks for the presence and accuracy of .cursorrules, CLAUDE.md, or AGENTS.md files.
    • Verify Loop Analysis evaluates if the install-build-test cycle is discoverable and fast enough for agent iteration.
    • Navigability Assessment identifies context-heavy files over 500 lines and identifies dead code that confuses LLMs.
    • Guardrail Review checks for CI integration and protections that prevent common agent-generated errors.
    • Scoring Engine assigns a 0 to 100 readiness score based on evidence-backed criteria.

    How it works

    1. The user triggers the audit on a specific repository or directory.
    2. The agent performs a read-only scan of manifests, documentation, and directory structures.
    3. The agent runs safe, dry-run commands to verify scripts and build paths.
    4. It generates a markdown report with a score breakdown, top issues, and quick wins.

    Frameworks & tools

    This tool works with any repository containing standard manifests like package.json, requirements.txt, or pyproject.toml. It specifically looks for configuration files for Cursor, Claude Dev, and GitHub Actions.

    Why this beats prompting it yourself

    Writing a custom prompt for a repo audit often leads to vague advice like "add more comments." This skill uses a weighted 100-point scoring system that prioritizes the verify loop and machine-readable instructions, ensuring you fix the technical blockers that actually stop agents from shipping code.

    Use cases

    • Onboarding agents to a legacy codebase that lacks structured documentation.
    • Optimizing Cursor/Claude performance by identifying context sinks and stale files.
    • Setting up new repos with an AGENTS.md starter based on discovered commands.

    Known limitations

    Does not automatically apply code fixes or refactors. Large repo scans are limited to safe, fast, dry-run commands and directory listing. Requires manual confirmation before running full install or test suites.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Prompt & Skill Engineering.

    Read-only by default. Requires manual confirmation for expensive build/test commands. Scores unknown dimensions as zero rather than guessing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Listed23 days ago

    What's inside

    Frequently Asked Questions

    The audit evaluates your repository across six dimensions, including instruction accuracy (like .cursorrules), navigability, and the efficiency of your build/test cycle, providing a 0-100 readiness score.

    This skill is designed to optimize any LLM-based tool, specifically enhancing the performance of Cursor, Claude Dev (Cline), GitHub Copilot, and custom autonomous agents that rely on repository context.

    No, the skill performs a read-only scan and safe dry-run commands; it identifies issues and provides a prioritized Markdown report, but you maintain full control over applying the suggested fixes.

    It is language-agnostic and works with any repository using standard manifests like package.json or requirements.txt, though it provides extra depth for projects using GitHub Actions and specific agent rule files.

    Extremely large repositories are scanned via directory structures and manifest analysis to remain fast, though the skill requires manual confirmation before attempting to analyze deep build or test suites in these environments.

    You receive the full audit skill, a comprehensive scoring engine, and a template for generating machine-readable 'AGENTS.md' files based on your specific project findings.

    New in Prompt & Skill Engineering

    Free