AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Agent Ready Fix

skill-risorseartificiali-agent-ready-skill-agent-ready-fix · by RisorseArtificiali

Remediate a project's agentic-readiness gaps by generating missing, project-specific files: AGENTS.md (primary, vendor-neutral) + target bridges, .env.example, .gitignore secret coverage, docs/agent-execution.md, CI + pre-commit baselines, Dependabot/Renovate, specs/ADR/issue templates, Makefile targets, and a generated repo index. Reads prior scores, prioritizes by impact, acts only on skill/par…

No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-risorseartificiali-agent-ready-skill-agent-ready-fix

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-risorseartificiali-agent-ready-skill-agent-ready-fix)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Agent Ready Fix? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Agent-Ready Fix — Remediate Readiness Gaps (v2)

Generate the missing, project-specific files that raise a codebase's agentic-readiness score. Brownfield by default: read prior scores, prioritize the highest-impact gaps, act only on what our skills can actually generate, and surface the rest as manual steps.

Canonical rubric: .claude/skills/agent-ready/references/scoring.md — the single source of truth for the 7 dimensions, sub-criterion ids, weights, layer tags, score math, and the v2 JSON schema. Do not re-derive numbers here.

Remediation registry: .claude/skills/agent-ready/references/remediation.md — keyed by the same ids; supplies fixable_by (skill|partial|manual), fix_ref, why, consequence, effort. This file decides what fix touches: act on skill and partial only; manual items are listed with their steps, never auto-generated.

Phase 0: ARGUMENTS

Parse $ARGUMENTS (order-independent):

  • dimension-id — an optional dimension or sub-criterion id (e.g. security_sandbox, secret_hygiene). If present, restrict remediation to that scope; else fix all impactful gaps.
  • path — first non-flag, non-id token: target dir (default cwd).
  • --agents — target list (claude,codex,opencode,pi). If absent, detect posture as scan does: AGENTS.md present → portable; a single dominant vendor dir (e.g. only .claude/) → infer that agent. Targets drive bridge generation only.

Phase 1: LOAD PRIOR SCORES

  1. Read .agent-ready/agent-ready-scores.json (v2 path; replaces v1 claudedocs/).
  2. If missing or schema_version != 2, invoke /agent-ready-scan [--agents ...] first, then re-read.
  3. Parse each dimension's raw_score and per-sub-criterion { score, fixable_by, na }.

Phase 2: PRIORITIZE

Rank gaps by impact = dimension_weight × (100 − raw_score) / 100 (highest first). Within a dimension, prioritize sub-criteria with the lowest score and fixable_by: skill over partial. If a dimension-id filter was given, keep only that scope. Skip any sub-criterion at 100 or na: true.

Phase 3: UNDERSTAND THE PROJECT

Before generating anything, read the project so output is contextual, never boilerplate:

  • Stack: pyproject.toml, package.json, go.mod, Cargo.toml, pom.xml, etc.
  • Commands: existing build/test/lint from Makefile, package.json scripts, pyproject.toml [tool.*], tox.ini. Use test_commands.py when python3 is available.
  • Tooling: ruff/eslint/prettier/rustfmt/mypy/tsconfig config present.
  • Structure & conventions: top-level dirs, naming style, workspace/monorepo boundaries.
  • Env vars: grep for os.environ/os.getenv/process.env/env::var/System.getenv references.
  • Existing artifacts: never plan to overwrite a file that exists.

Phase 4: SELECT GENERATORS

For each prioritized gap, map its sub-criterion id to a generator below (fixable_by: skill|partial only). Each generator produces real, detected content. manual sub-criteria are collected for Phase 6 instead.

Dim 1 — Agent Instructions & Context

  • primary_instruction_file / instruction_quality (skill/partial): generate AGENTS.md as the PRIMARY instruction file — concise, ** and write a generated repo index (top-N ranked files/symbols) to .agent-ready/repo-index.md; link it from AGENTS.md`.
  • readme_overview (partial): scaffold a README skeleton (purpose, setup, usage, structure) from the detected stack — only if README is absent or very sparse.

Dim 3 — Testing & Feedback

  • test_commands_documented (skill): document the detected test command(s) in AGENTS.md and add Makefile test/lint targets when no task runner exists.
  • fast_feedback_loop (partial): document a quick-subset command convention.
  • feedback_quality (partial): scaffold a type-checker config (mypy.ini/[tool.mypy] or tsconfig strict) for the stack.
  • coverage_reasonable (partial): scaffold a coverage config + target (pytest-cov/coverage/nyc).

Dim 4 — CI/CD, Automation & Governance

  • ci_runs_tests_lint (skill): generate .github/workflows/ci.yml (or ecosystem equivalent) running the detected test + lint commands.
  • lint_format_automated (skill): add a baseline linter/formatter config for the stack and wire it into Makefile/CI.
  • pre_commit_hooks (skill): generate .pre-commit-config.yaml wired to the detected lint/format/secret tools.
  • governance (skill): generate a CODEOWNERS skeleton and a Dependabot (.github/dependabot.yml) or Renovate (renovate.json) config for detected ecosystems.

Dim 5 — Agent Tooling & Capabilities

  • standard_skills / bundled_helper_scripts (partial): scaffold a conformant SKILL.md + scripts/ skeleton in a standard path.
  • mcp_declaration (skill): generate a baseline .mcp.json with an honest per-vendor portability note.

Dim 6 — Security & Sandbox

  • documented_execution_policy (skill): generate docs/agent-execution.md — vendor-neutral documented sandbox/execution policy listing LINCE among devcontainer / OS-sandbox / hosted options, plus a safe-to-run command list. This is where non-detectable runtime sandboxes earn credit.
  • secret_hygiene (partial): add secret patterns to .gitignore (.env, *.pem, id_rsa, *credentials*, *.key) and generate a redacted .env.example from discovered env-var refs (no real values). Note: enabling host secret scanning + push protection is the manual half.
  • committed_isolation_config (partial): scaffold a .devcontainer/ note/template with a default-deny egress allowlist; hardening to true isolation is human work.
  • supply_chain_pinning (partial): generate Dependabot/Renovate config and flag any gitignored lockfiles (uv.lock/package-lock.json/Cargo.lock/go.sum) to commit.

Dim 7 — Spec-Driven Workflow & Docs

  • spec_tasks_dir (skill): scaffold specs/TEMPLATE.md (delta-scoped task template with an acceptance-criteria section).
  • issue_pr_templates (skill): generate .github/ISSUE_TEMPLATE/feature.yml + bug.yml and a PR template.
  • adr_decisions (partial): scaffold docs/adr/0001-record-architecture-decisions.md (ADR template).
  • docs_comprehension_signals (partial): scaffold an ARCHITECTURE.md skeleton and a CHANGELOG.md; report type/docstring coverage gaps from coverage_signals.py.

Phase 5: CONFIRMATION GATE

List every file to be created or appended, then wait for explicit approval. Show what each does and mark files that already exist as skipped. Do not write anything before approval.

## Files to Generate (impact-ordered)

1. ✨ AGENTS.md — primary instructions: build/test/lint, structure, conventions ( [--agents ...]`) to recompute scores, then show a before/after delta:

🔧 Agent-Ready Fix Results

Files Generated

  • ✅ AGENTS.md, CLAUDE.md (symlink), docs/agent-execution.md, .env.example, .pre-commit-config.yaml, specs/TEMPLATE.md
  • ➕ .gitignore (secret patterns appended)

Score Delta

Before After Change Agent Instructions & Context 9.0 14.4 +5.4 📈 Security & Sandbox 3.6 8.4 +4.8 📈 CI/CD, Automation & Governance 4.2 9.8 +5.6 📈 Spec-Driven Workflow & Docs 2.5 6.0 +3.5 📈 ────────────────────────────────────────────────────── Overall 48 67 +19 📈 Level 🟡 Partial 🟢 Ready

Still Manual

  • semanticnavamenability (High) · testsuitepresent (High) · navcomprehensionmcp_servers (Med)

## Critical Rules

- **NEVER overwrite existing files** — create new, or append to existing where sensible.
- **`remediation.md` is authoritative** — act only on `fixable_by: skill|partial`; surface `manual` with steps.
- **AGENTS.md is primary** — vendor-neutral, < 200 lines; bridge to `claude` via symlink; codex/opencode/pi read it natively (no drift-prone copies).
- **Contextualize everything** — read the project first; real, detected content only, no boilerplate or placeholders.
- **Confirmation gate** — always list files and wait for approval before writing.
- **Respect `.gitignore`** and match existing naming/formatting/structure conventions.
- **Always show the before/after delta** by re-running the scan logic.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [RisorseArtificiali](https://github.com/RisorseArtificiali)
- **Source:** [RisorseArtificiali/agent-ready-skill](https://github.com/RisorseArtificiali/agent-ready-skill)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.