Terminal
Terminal/Skill
Edits repo-backed Markdown and MDX docs, blogs and resources, with local components and shareable copies.
By Builder.io
Works with
npx skills add builderio/agent-native --skill contentUse 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.
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.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.agent-native.json; SQL remains cache/history/search glue, not the source of
truth for those pages..md/.mdx files directly, preserve frontmatter and MDX imports, and tell
the user the Content action surface was not available.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.
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.
components folder. Components
should be PascalCase exports from .tsx files; simple editable input metadata
can live next to them as ComponentNameInputs.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.