agentleFS
mystilleefmystilleef/spae-framework/skills/structure/SKILL.md

structure

Skill2 starsChanged 14 days agoMITView on GitHub

Orchestrates refactoring agents sequentially to fix structural violations.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run refactoring subagents sequentially to fix structural violations in target code.

    line 19
  2. Distinctive:

    Always use the subagent tool for subagent invocation.

    line 42
  3. Distinctive:

    Never run subagents in parallel or concurrently.

    line 53
  4. Distinctive:

    Every run, halted or not, ended in Report.

    line 63
  5. Distinctive:

    Keep prose terse while ensuring clarity.

    line 70
  6. Distinctive:

    Use lists and sub-lists for long sentences and dense paragraphs.

    line 73

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Structure

When to use

  • The user wants to fix structural violations autonomously using the refactor agent.

Goal

  • Run refactoring subagents sequentially to fix structural violations in target code.

Input

  • Accept optional arguments (file or folder paths).

Workflow

Halt on any Halt conditions entry after every spawn.

  1. Refactoring Loop:
    • Spawn a refactor subagent with the optional argument; await its result.
    • Complete: repeat step 1.
    • No Changes: proceed to step 2.
  2. Report: emit the result per Result directives:
    • Result: Completed when the workflow reaches Report without a halt; Halted when a subagent reports Failed; Failed on any other Halt conditions entry.

Directives

  • Always use the subagent tool for subagent invocation.
  • Pass the argument verbatim to each subagent; never read or expand file-path arguments.
  • Route only from each subagent's Result value.
  • Spawn only the subagents the workflow names.

Constraints

  • Restrict activities to spawning subagents, reading their results, and reporting; never write files, run git operations, activate skills, or prompt the user mid-run.
  • Never run subagents in parallel or concurrently.
  • Halt conditions: halt immediately; report per Report, listing the diagnostic under Findings:
    • A subagent Failed result.
    • A subagent result missing or outside the workflow's literals.
    • A process failure (crash, timeout, AgentError).

Verification

  • Subagents ran one at a time, in workflow order.
  • Every run, halted or not, ended in Report.
  • The orchestrator wrote no file.

Result directives

  • Minimum words. Maximum signal.
  • Return the final execution status block.
  • Keep prose terse while ensuring clarity.
  • Optimize prose for agent, token, and context efficiency.
  • Split actions, findings, and summaries into terse bullet points.
  • Use lists and sub-lists for long sentences and dense paragraphs.
  • Emit the result template as live markdown—never in a code fence.
  • Output nothing outside the template.

Result template

<!-- prettier-ignore-start -->
### Execution Summary

- **Actions**:
  - [Terse list of actions from spawned subagents]
- **Files**:
  - [Terse list of files affected by spawned subagents]
- **Findings**:
  - [Terse list of findings from spawned subagents]
- **Summary**:
  - [Terse list of summary from spawned subagents]

> **Structure Status** • `[scope]`
> **Result**: [Completed | Halted | Failed]
> **Impact**: [Terse impact statement]
<!-- prettier-ignore-end -->

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.