agent-readiness

Evaluate repository discoverability, adoptability, and extensibility for autonomous coding agents.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill agent-readiness-anthony-chaudhary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-readiness
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/agent-readiness
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill agent-readiness-anthony-chaudhary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the friction and discovery issues that prevent autonomous coding agents from successfully adopting and building upon a repository.

Core Features & Use Cases

  • Friction-Debt Tracking: Identifies concrete, re-derivable defects that block agent adoption, such as missing entry points or broken installation commands.
  • Experience-Frontier Measurement: Tracks the growth of real, working agent affordances like integration recipes and zero-setup harness configurations.
  • Use Case: Use this skill after modifying agent-facing surfaces like AGENTS.md or integration recipes to ensure the repository remains the path of least resistance for an AI agent.

Quick Start

Run the agent-readiness scorecard to identify and retire friction-debt in the current repository.

Frequently Asked Questions about agent-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is agent-first repository readiness and why does it matter?

Agent-first repository readiness measures how easily autonomous coding agents can discover, adopt, and build upon a codebase by identifying friction-debt and evaluating agent affordances across the git-tracked tree.

How do I score my repository for autonomous agent adoptability?

You score repository adoptability by running the agent-readiness scorecard against the repository structure and documentation to measure friction-debt defects and experience-frontier growth.

Do I need a Go environment to evaluate repository health for AI agents?

Yes, you need a Go environment to execute the scorecard against the repository structure and documentation to evaluate agent-friendly interfaces.

What is friction-debt in an agent-facing repository?

Friction-debt refers to concrete, re-derivable defects that block agent adoption, such as missing entry points or broken installation commands within the repository.

When should I run an agent-readiness scorecard on my repository?

You should run the scorecard after modifying agent-facing surfaces like AGENTS.md or integration recipes to ensure the repository remains the path of least resistance for an AI agent.

What's the best way to track experience-frontier metrics for autonomous coding agents?

The best way to track experience-frontier metrics is measuring the growth of real, working agent affordances like integration recipes and zero-setup harness configurations across the git-tracked tree.