How do I install the Askit Build Agents Md skill?

Run npx skillmds@latest add product-on-purpose/askit-build-agents-md in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Askit Build Agents Md safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Askit Build Agents Md?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Askit Build Agents Md free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Askit Build Agents Md?

product-on-purpose (@product-on-purpose) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Askit Build Agents Md by product-on-purpose

Name: Askit Build Agents Md
Author: product-on-purpose

Askit Build Agents Md

Creates and improves a plugin's AGENTS.md (the agent navigation and instructions entrypoint) to the Advanced Skill Library Standard. Use when you need to author or sync AGENTS.md, align it with the component index, or trim an overgrown one to essential, mostly-positive guidance.

File contents

askit-build-agents-md

Purpose

Author and keep current a plugin's AGENTS.md: the project-level agent instructions and navigation entrypoint, the first thing an agent reads (Standard sec 3.10). It is the single most portable cross-tool surface (Claude, Codex, Gemini, Copilot, and Cursor all read AGENTS.md). Two modes: create authors a tight AGENTS.md; improve syncs it to the component index and trims it. Authoring depth is in references/authoring-agents-md.md. Follows the shared builder contract (../../docs/reference/builder-pattern.md).

When to use

When the user asks to author, write, sync, or trim AGENTS.md (or CLAUDE.md), or when components were added or removed and the navigation is stale.

create mode

Brief interview: what the project is, the conventions (runtime, build/test/lint), and the boundaries. Skip if in context.
Author a TIGHT AGENTS.md: what-this-is, current-state (read before assuming capabilities), conventions, build/test/lint, where-to-look. Keep it minimal and essential-only, and prefer positive instructions over long "do not" lists. Verbose, generated-looking context files measurably reduce agent task success and raise cost, so brevity is a feature, not a shortcut.
Keep the component list aligned with library.json and the index. node scripts/generators/sync-agents-md.mjs renders the component section from the manifest so it does not drift.
Evaluate (node scripts/evaluate.mjs . --json); AGENTS.md presence is checked by U2 (anatomy), and the description and instruction-budget rules apply.

improve mode

Run evaluate and read findings; sync the component list to disk.
Trim: remove redundancy and non-essential prohibitions; judge each change by whether it helps an agent act correctly, not by length.
Re-run to confirm.

Scope

AGENTS.md is Universal-tier and the cheapest credible cross-tool surface. Keep it brief and current; the generated component section (sync-agents-md) prevents drift from the manifest. A CLAUDE.md is a Claude-specific sibling for the same purpose when a project needs Claude-only guidance.

---name: askit-build-agents-mddescription: Creates and improves a plugin's AGENTS.md (the agent navigation and instructions entrypoint) to the Advanced Skill Library Standard. Use when you need to author or sync AGENTS.md, align it with the component index, or trim an overgrown one to essential, mostly-positive guidance.---# askit-build-agents-md## PurposeAuthor and keep current a plugin's `AGENTS.md`: the project-level agent instructions and navigation entrypoint, the first thing an agent reads (Standard sec 3.10). It is the single most portable cross-tool surface (Claude, Codex, Gemini, Copilot, and Cursor all read `AGENTS.md`). Two modes: `create` authors a tight AGENTS.md; `improve` syncs it to the component index and trims it. Authoring depth is in [references/authoring-agents-md.md](references/authoring-agents-md.md). Follows the shared builder contract ([../../docs/reference/builder-pattern.md](../../docs/reference/builder-pattern.md)).## When to useWhen the user asks to author, write, sync, or trim `AGENTS.md` (or `CLAUDE.md`), or when components were added or removed and the navigation is stale.## create mode1. Brief interview: what the project is, the conventions (runtime, build/test/lint), and the boundaries. Skip if in context.2. Author a TIGHT AGENTS.md: what-this-is, current-state (read before assuming capabilities), conventions, build/test/lint, where-to-look. Keep it minimal and essential-only, and prefer positive instructions over long "do not" lists. Verbose, generated-looking context files measurably reduce agent task success and raise cost, so brevity is a feature, not a shortcut.3. Keep the component list aligned with `library.json` and the index. `node scripts/generators/sync-agents-md.mjs` renders the component section from the manifest so it does not drift.4. Evaluate (`node scripts/evaluate.mjs . --json`); AGENTS.md presence is checked by U2 (anatomy), and the description and instruction-budget rules apply.## improve mode1. Run evaluate and read findings; sync the component list to disk.2. Trim: remove redundancy and non-essential prohibitions; judge each change by whether it helps an agent act correctly, not by length.3. Re-run to confirm.## ScopeAGENTS.md is Universal-tier and the cheapest credible cross-tool surface. Keep it brief and current; the generated component section (`sync-agents-md`) prevents drift from the manifest. A `CLAUDE.md` is a Claude-specific sibling for the same purpose when a project needs Claude-only guidance.

Frequently asked questions