agentsclimarketplace

Write agent brief

Skill Mergemat/agent-readiness-skills/skills/write-agent-brief

Harness-agnostic skills for agent-readable repos and task prep

Install
npx -y skills add Mergemat/agent-readiness-skills --skill write-agent-brief

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Writes a durable implementation brief for an agent without overfitting to current file paths. Use when user wants to turn context, a bug report, PRD, plan, or conversation into an agent-ready issue, task brief, or implementation contract.

SKILL.md

1.3 KB, 218 tokens by cl100k_base, as published. Nobody here has run it

Write Agent Brief

Write the contract an implementation agent can work from later.

Prefer behavior and interfaces over file paths. File paths go stale; contracts survive.

Process

  1. Read the current context and any task packet.
  2. Separate current behavior from desired behavior.
  3. Name key interfaces, data shapes, commands, and user-visible behavior.
  4. State acceptance criteria as independent checks.
  5. State out of scope explicitly.
  6. Add human review or approval needs.

Use brief-format.md for a formal brief.

Rules

  • Do not include line numbers.
  • Avoid file paths unless the path itself is the contract.
  • Do not prescribe implementation steps unless the user asked for a plan.
  • Include verification commands when known.
  • If requirements are ambiguous, list questions instead of inventing.

Output

Return a brief ready to paste into an issue, PRD, or task tracker.

If publishing to an issue tracker, follow the repo's configured issue tracker docs. If no tracker is configured, only produce markdown.

What ships with it: 1 file

795 B alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,984. 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.