aim-evaluate-readme

Evaluate README claims against the origin/main baseline and output alignment gaps.

4|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/zccz14/AIM --skill aim-evaluate-readme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aim-evaluate-readme
Source: https://github.com/zccz14/AIM/tree/main/.agents/skills/aim-evaluate-readme
Command: npx skills add https://github.com/zccz14/AIM --skill aim-evaluate-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates README claims against the latest origin/main baseline to surface alignment gaps between stated goals and the actual baseline facts.

Core Features & Use Cases

  • Compare README statements to the current origin/main facts and produce structured evidence (claim_checks) and a clear directional output (iteration_signal) for the Coordinator.
  • Produce a concise gap_summary and an open_questions list to guide clarifications without creating tasks or execution decisions.
  • Support scenarios where READMEs need alignment, clarification, or disambiguation before any task planning.

Quick Start

Provide the README text and the latest origin/main baseline facts to run the evaluation and generate scope, claim_checks, conclusion_category, iteration_signal, gap_summary, and open_questions.

Frequently Asked Questions about aim-evaluate-readme

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

FAQPage Schema
How do I evaluate README claims against the origin/main baseline?

To evaluate README claims, provide the README text and the latest origin/main baseline facts to generate structured claim_checks, scope, and a gap_summary identifying alignment discrepancies.

What is gap analysis for README alignment and when do I need it?

README gap analysis compares stated goals against actual baseline facts to surface alignment gaps. You need it when READMEs require clarification or disambiguation before initiating any task planning.

Can I generate direction signals for a coordinator without creating tasks?

Yes, you can generate a direction signal for the coordinator by producing an iteration_signal and open_questions list that guide clarifications, explicitly without creating tasks or deciding what to implement.

What do I need to provide to run a README baseline evaluation?

You need to provide the README text and the latest origin/main baseline facts. The evaluation uses these inputs to output conclusion_category, claim_checks, and gap_summary without requiring external dependencies.

Does README gap analysis output execution decisions or task lists?

No, README gap analysis does not output execution decisions or task lists. It strictly produces a gap_summary, open_questions, and iteration_signal to guide the coordinator before any task planning occurs.