agentleFS
CodeCaroSCodeCaroS/MythOs_Aegis/.agents/skills/output-templates/SKILL.md

output-templates

Skill0 starsChanged 3 months agoApache-2.0View on GitHub

Infrastructure skill providing shared output-format components (direct, review, plan, execution, decision, status, research, optimization, artifact profiles) that other skills compose in their final-output section. Not typically invoked directly by a user request.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these templates as the default shape in substantive responses.

    line 18
  2. Distinctive:

    Use reusable components and named profiles.

    line 124

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Output Templates

Use these templates as the default shape in substantive responses.

Direct Answer

Conclusion first.

Reason:

- Fact / evidence 1
- Fact / evidence 2

Next step:
1. Concrete action
2. Verification step

Partial Completion

Completed:
- What was done

Still open:
- What remains

Needed next:
- Exact input, permission, file, or decision

Blocked

Blocked because <specific reason>.

To proceed, I need:
- Exact unblocker

Review Finding

## Findings

1. Severity, location, and issue.
2. Severity, location, and issue.

## Risk

- Why it matters

## Recommendation

- Smallest fix that addresses the root cause

Plan

## Goal

<one sentence>

## Approach

1. First step
2. Second step
3. Check

## Acceptance Criteria

- Checkable condition that defines done

Test Result

Tested:
- Command or suite

Result:
- Pass or fail

Notes:
- Relevant limitation or failure detail

Handoff

## What Changed

- Files or behavior changed

## What Remains

- Open work

## Where to Continue

- Exact file, command, or module

Shared output profile

Compose the direct profile from output-templates. Use reusable components and named profiles; omit empty sections and preserve owning-skill fields. Preserve stricter domain rules above, omit empty components, and never fill a component with invented evidence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.