agentleFS
Sign inStart free
BuilderIOBuilderIO/agent-native/skills/content/SKILL.md

content

Skill7.6k starsChanged 5 months agoMITView on GitHub

Use Content for repo-backed Markdown/MDX docs, blogs, resources, rich document editing, local components, shareable copies, and Content local-file workspaces. Prefer Content actions over raw filesystem writes when available.

We split this skill into the rules it gives an agent

10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the Content app when a workflow is about authoring, editing, reviewing, or publishing Markdown/MDX documents: docs sites, blogs, …

    line 13
  2. Very specific:

    Use Content actions when the Content MCP/action tools are available: list-documents, search-documents, get-document, pull-document, …

    line 21
  3. Very specific:

    Use pull-document or get-document before editing a page.

    line 26
  4. Distinctive:

    If Content tools are not visible and no local Content app or Desktop bridge is running, treat this skill as repo-editing guidance.

    line 32
  5. Distinctive:

    Prefer JSON input for action calls:

    line 39
  6. Very specific:

    Run refresh-list after create/update/delete operations when you need the open Content UI sidebar to repaint immediately.

    line 49
  7. Very specific:

    Use local components from the configured components folder.

    line 113
  8. Very specific:

    Use list-local-component-files and write-local-component-file for component source changes when Content tools are available.

    line 116
  9. Distinctive:

    Do not push/pull Notion, Builder.io, or other provider-backed content unless the user explicitly asks for provider sync.

    line 125
  10. Distinctive:

    Do not paste secrets, private provider data, or credential-looking values into docs, generated pages, frontmatter, examples, or local …

    line 127

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

Content

Use the Content app when a workflow is about authoring, editing, reviewing, or publishing Markdown/MDX documents: docs sites, blogs, resource libraries, marketing pages, internal notes, and local MDX components. Content gives the agent a document tree, a rich editor, normal document actions, and optional local-file source of truth.

Choose The Path

  • Use Content actions when the Content MCP/action tools are available: list-documents, search-documents, get-document, pull-document, create-document, edit-document, update-document, delete-document, share-local-file-document, list-local-component-files, and write-local-component-file.
  • Use pull-document or get-document before editing a page. Use edit-document for precise find/replace changes and update-document for full rewrites or new content.
  • In Local File Mode, Content actions read and write the repo files declared in agent-native.json; SQL remains cache/history/search glue, not the source of truth for those pages.
  • If Content tools are not visible and no local Content app or Desktop bridge is running, treat this skill as repo-editing guidance. Edit configured .md/.mdx files directly, preserve frontmatter and MDX imports, and tell the user the Content action surface was not available.

Action Examples

Prefer JSON input for action calls:

pnpm action list-documents
pnpm action get-document '{"id":"local-file:..."}'
pnpm action edit-document '{"id":"local-file:...","find":"old copy","replace":"new copy"}'
pnpm action update-document '{"id":"local-file:...","content":"# Updated\n\nBody"}'
pnpm action share-local-file-document '{"id":"local-file:..."}'

Run refresh-list after create/update/delete operations when you need the open Content UI sidebar to repaint immediately.

Local File Mode

Install into an existing repo with:

npx @agent-native/core@latest skills add content --mode local-files --scope project

The installer copies this skill and writes or updates agent-native.json with Content roots for docs/, blog/, content/, and resources/, plus a components/ folder for local MDX components. A typical manifest looks like:

{
  "version": 1,
  "apps": {
    "content": {
      "mode": "local-files",
      "roots": [
        {
          "name": "Docs",
          "path": "docs",
          "kind": "docs",
          "extensions": [".md", ".mdx"]
        },
        {
          "name": "Blog",
          "path": "blog",
          "kind": "blog",
          "extensions": [".md", ".mdx"]
        },
        {
          "name": "Content",
          "path": "content",
          "kind": "content",
          "extensions": [".md", ".mdx"]
        },
        {
          "name": "Resources",
          "path": "resources",
          "kind": "resources",
          "extensions": [".md", ".mdx"]
        }
      ],
      "components": "components",
      "extensions": "extensions",
      "hide": ["**/_*.md", "**/_*.mdx"]
    }
  }
}

Local File Mode does not make the host language model local, and the hosted Content app cannot read private repo files by itself. File access requires a local Content app, Agent-Native Desktop, or another trusted local bridge.

MDX And Components

  • Preserve frontmatter keys you do not understand. Preserve MDX imports, exports, JSX, and expression props unless the user explicitly asks to change them.
  • Use local components from the configured components folder. Components should be PascalCase exports from .tsx files; simple editable input metadata can live next to them as ComponentNameInputs.
  • Use list-local-component-files and write-local-component-file for component source changes when Content tools are available. Otherwise edit the component files directly like normal repo source.

Boundaries

  • Moving, renaming, and reordering local-file pages are not first-class Content UI operations yet. Use normal file operations when the user asks for those, then let Content rediscover the file tree.
  • Do not push/pull Notion, Builder.io, or other provider-backed content unless the user explicitly asks for provider sync.
  • Do not paste secrets, private provider data, or credential-looking values into docs, generated pages, frontmatter, examples, or local components.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about BuilderIO/agent-native

The biggest 5 of 61 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 61

Talked about on GitHub and Bluesky (61 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 11

6 more on Bluesky

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