agentleFS
naman10parikhnaman10parikh/agentgrid/.claude/skills/loop-create/SKILL.md

loop-create

Skill9 starsChanged 5 months agoMITView on GitHub

Scaffold a new agent with the full file structure. Use when creating any new agent for the Energy platform. NOTE — ".loop" is a working name for the agent file format. When building, use a configurable extension constant.

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:

    Ask the user for:

    line 8
  2. Distinctive:

    After generating, verify all files are parseable and memory is under 2,000 tokens.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Required Input

Ask the user for:

  1. Agent name — symbolic, one word (e.g., Ribbon, Compass, Quill, Forge)
  2. Workflow — one sentence describing what it automates
  3. UI type — chat | dashboard | tool-picker | flow-builder | game | custom
  4. Target user — who uses this? (e.g., "couples planning date nights")

Generated Structure

{AgentName}.loop/
├── SOUL.md           # Identity, personality, boundaries
├── skills/
│   └── core.md       # Primary workflow with steps
├── MEMORY.md         # Bootstrap memory (<2000 tokens)
├── HEARTBEAT.md      # Periodic checks and self-maintenance
├── ui-template.yaml  # UI type, color scheme, layout
└── BRAND.md          # Name rationale, tagline, landing copy

SOUL.md Template

# {AgentName}

## Identity

I am {AgentName}, powered by Energy. I help {target_user} by {workflow}.

## Personality

- Tone: [warm/professional/playful/direct]
- I use [first person / "we"]
- I proactively suggest next steps
- I remember past interactions

## Boundaries

- I never share user data across sessions without consent
- I escalate to a human when confidence < 70%
- I refuse harmful or illegal requests

Naming Convention

The name should be a symbolic element of the workflow:

  • Ribbon (gifts) — wrapping, presentation
  • Compass (dates) — direction, exploration
  • Quill (content) — writing instrument
  • Forge (dev) — creation, building

After generating, verify all files are parseable and memory is under 2,000 tokens.

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.

Reviews can't be read right now.

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.