agentsclimarketplace

Create agents md

Skill MSiccDev/ai-context-kit/skills/create-agents-md

Create concise, repository-specific AGENTS.md files with operational contract, precedence rules, and drift-control guidance.From its SKILL.md

Install
npx -y skills add MSiccDev/ai-context-kit --skill create-agents-md

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 482 tokens by cl100k_base, as published. Nobody here has run it

Create AGENTS.md

Purpose

Generate a complete root AGENTS.md file that acts as an operational entrypoint while preserving source-of-truth and repository governance rules.

When To Use

  • Use this skill when adding or refreshing repository AGENTS.md.
  • Use this skill when repository map, precedence, and session controls must be documented concisely.
  • Do not use this skill for project/user instruction file generation.

How to Invoke

Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/create-agents-md/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.

Required Inputs

  • Repository purpose and canonical paths.
  • Source precedence and key references.
  • Session-state defaults and command namespace rules.
  • Drift-control requirements.

Workflow

  1. Run seven-phase discovery using references/discovery-phases.md.
  2. Apply required element contract from references/required-elements.md.
  3. Generate artifact using references/output-format.md.
  4. Stamp <!-- spec_version: 1.4.3 --> as an HTML comment at the top of the generated AGENTS.md.
  5. Validate result against references/quality-checklist.md.
  6. Ensure links/paths remain relative and repository-accurate.

Output Expectations

  • One complete root AGENTS.md file.
  • Includes purpose, precedence, repo map, command policy, and drift-control.
  • Uses provider-neutral wording and valid relative links.
  • Remains scannable and operationally actionable.
  • Output contract and summary format follow references/output-format.md.

Resources

  • Discovery workflow: references/discovery-phases.md
  • Required element contract: references/required-elements.md
  • Output contract: references/output-format.md
  • Quality checklist: references/quality-checklist.md
  • Canonical template: ../../templates/AGENTS_template.md
  • Repository example: ../../AGENTS.md

Constraints And Safety

  • Do not duplicate full normative specs in AGENTS.
  • Preserve canonical path stability.
  • Keep guidance deterministic and testable.
  • Use relative path references only.

What ships with it: 5 files

4.1 KB alongside SKILL.md

Gives 0 of the 12 instructions most memory context skills give in 482 tokens

Counted across 754 of the 1,056 authors here whose files we hold, read 2026-09-06

  • Preserve existing content structurein 15 of 754, across 9 files
  • Front-load the leading wordin 14 of 754, across 10 files
  • Update existing entries instead of duplicatingin 14 of 754, across 7 files
  • Keep CLAUDE.md under one hundred linesin 14 of 754, across 12 files
  • Read CLAUDE.md at the project rootin 14 of 754
  • Keep each meaning in a single source of truthin 12 of 754, across 8 files
  • Redact sensitive information before committingin 11 of 754, across 4 files
  • Scan for all CLAUDE.md filesin 11 of 754, across 7 files
  • Use frontmatter for metadata on filesin 10 of 754, across 3 files
  • Repeat user interactions 10 timesin 10 of 754, across 4 files
  • Write the CLAUDE.md file into the target folderin 10 of 754, across 8 files
  • Use memlab to process snapshotsin 9 of 754, across 3 files

Said here and by no other author read

  • Run phased discovery using the reference document
  • Stamp the spec version comment at the top
  • Validate completeness using the quality checklist
  • Apply required element contract
  • Generate artifact using output format
  • Ensure links remain relative and accurate

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.