agentleFS
Sign inStart free
BlockKnown publisherblock/berd/distro/skills/agent-builder/SKILL.md

agent-builder

Skill1k starsChanged 3 months agoApache-2.0View on GitHub

Create, edit, or inspect Berd agents/personas stored as Agent Markdown files with YAML frontmatter under ~/.agents/agents. Use when user needs to manage Berd agents or personas.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use this skill when managing Berd agents/personas in Agent Markdown format.

    line 11
  2. Distinctive:

    Default to global unless the user asks for project-local.

    line 20
  3. Distinctive:

    Use platform path APIs or shell-safe home expansion.

    line 21
  4. Very specific:

    Write <slug>.md; on create collisions, use <slug>-2.md, <slug>-3.md, etc.

    line 48
  5. Distinctive:

    When editing, read the existing file first.

    line 51
  6. Distinctive:

    Prefer direct file edits over helper scripts.

    line 53
  7. Very specific:

    After writing, verify that the file exists, frontmatter is valid, name and description are both trimmed and non-empty, and preserved …

    line 55

“Common” is measured: kept by at least 6 in 10 of the 49 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

Agent Builder

Use this skill when managing Berd agents/personas in Agent Markdown format.

Storage

Agents are UTF-8 Markdown files with YAML frontmatter:

  • Global: ~/.agents/agents/<slug>.md
  • Project-local: <project>/.agents/agents/<slug>.md

Default to global unless the user asks for project-local. Use platform path APIs or shell-safe home expansion.

Format

Each agent is one .md file:

---
name: Agent Name
description: A concise summary of what this agent does
provider: optional-provider
model: optional-model
avatar: optional-avatar
---

Agent instructions here.

Required frontmatter keys are name and description. The description must be a trimmed, non-empty summary of what the agent does; never create or save an agent with a missing, blank, or placeholder description. If the user has not supplied enough context to write an accurate description, ask for one before saving. Preserve all other frontmatter keys when editing existing agents unless the user explicitly changes them. The Markdown body is the agent’s system prompt/persona instructions.

When writing or generating a description or body, do not assign the agent a gender or gendered pronouns unless the user asked for one. Use it/its or they/them for the agent, matching how it is framed (tool vs. character), or avoid pronouns; people the instructions describe get they/them. Preserve pronouns the user chose, in either direction.

Names and Slugs

For create/rename, require a trimmed name that is non-empty, ≤80 characters, and contains no / or \.

Derive <slug> from the name by lowercasing, replacing each non-ASCII alphanumeric run with -, collapsing/trimming -, truncating to 64 characters, and falling back to agent.

Write <slug>.md; on create collisions, use <slug>-2.md, <slug>-3.md, etc.

Workflow

When editing, read the existing file first. Resolve targets by exact path, frontmatter name, then slug filename. Ask only if multiple matches remain.

Prefer direct file edits over helper scripts. Do not require Python, Node, or another runtime unless the current repo already requires it.

After writing, verify that the file exists, frontmatter is valid, name and description are both trimmed and non-empty, and preserved metadata was not removed. Report the final path.

Download now (ZIP)

  • Other versions54 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 54

    1. shareAI-lab/learn-claude-code★ 80ksame name
    2. shareAI-lab/analysis_claude_code★ 78ksame name
    3. NangoHQ/nango★ 13ksame name
    4. DenchHQ/DenchClaw★ 1.7ksame name
    5. DenchHQ/ironclaw★ 1.7ksame name
    6. Mathews-Tom/armory★ 340same name
    7. Southclaws/storyden★ 339same name
    8. FareedKhan-dev/claude-code-from-scratch★ 296same name
    9. wulawulu/learn-claude-code-rs★ 154same name
    10. pr-pm/prpm★ 124same name

    44 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use workflow-builder, pdf and 7 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • Hussain-ElfalahSkill

      workflow-builder

      Also in 3 projects that use this

    • AnthropicSkill

      pdf

      Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

      Also in 27 projects that use this

    • MicrosoftSkill

      mcp-builder

      Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

      Also in 27 projects that use this

    • dragonflydbSkill

      benchmark

      Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

      Also in 3 projects that use this

    • SentrySkill

      onboard

      Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

      Also in 3 projects that use this

    • OpenAISkill

      audit

      Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

      Also in 3 projects that use this

  • In this repository18 other files it gives its agents.

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.

Check your setup, free