export declare const CONTENT_SKILL_MD = "---\nname: content\ndescription: >-\n  Use Content for repo-backed Markdown/MDX docs, blogs, resources, rich\n  document editing, local components, shareable copies, and database-backed\n  local-folder sources. Prefer Content actions over raw filesystem writes when\n  available.\nmetadata:\n  visibility: exported\n---\n\n# Content\n\nUse the Content app when a workflow is about authoring, editing, reviewing, or\npublishing Markdown/MDX documents: docs sites, blogs, resource libraries,\nmarketing pages, internal notes, and local MDX components. Content gives the\nagent a document tree, a rich editor, normal document actions, and optional\nlocal-folder synchronization.\n\n## Connect Content\n\nIf Content actions are already visible, use them. Otherwise connect the host to\nthe Content app descriptor's hosted MCP URL (the hosted service uses\n`https://content.agent-native.com/mcp`). OAuth-capable hosts should add that\nremote MCP URL and let the user complete the host-owned sign-in and consent\nstep. Claude uses its custom Connectors flow; Claude Code adds the same remote\nHTTP URL and authenticates from `/mcp`; ChatGPT/OpenAI, Cursor, Grok/xAI, and\nother OAuth-capable MCP hosts use their custom connector or MCP settings.\n\nUse the browser for OAuth or consent, an MCP App or focused artifact handoff,\nor interaction that genuinely exists only in the UI. When Content actions are\navailable, do not replace Content reads, analysis, or ordinary changes with\nbrowser automation. After authorization, inspect the tools the host actually\nprovides and use only those tools; do not infer unavailable capabilities from\nthis skill.\n\nCodex and Claude Cowork do not use remote MCP OAuth. Open the app's\n`/mcp/connect` page or run\n`npx @agent-native/core@latest connect https://content.agent-native.com` for\ntheir browser-authorized device-code flow. Other clients without remote OAuth\nuse the same fallback. Never ask the user to paste a token into chat.\n\n## Choose The Path\n\n- Use Content actions when the Content MCP/action tools are available:\n  `list-documents`, `search-documents`, `get-document`,\n  `pull-document`, `create-document`, `edit-document`,\n  `update-document`, `delete-document`,\n  `sync-manifest-local-folder-source`, `sync-local-folder-source`,\n  `list-local-component-files`, and `write-local-component-file`.\n- Use `pull-document` or `get-document` before editing a page. Use\n  `edit-document` for precise find/replace changes and `update-document`\n  for full rewrites or new content.\n- Local folders declared in `agent-native.json` are sources for ordinary\n  SQL-backed Content pages. Use the trusted bridge's pull/check/push workflows to\n  synchronize them; normal document actions always operate on the database.\n- If Content tools remain unavailable after the applicable hosted connection\n  path, and no local Content app or Desktop bridge is running, treat this skill\n  as repo-editing guidance. Edit configured\n  `.md`/`.mdx` files directly, preserve frontmatter and MDX imports, and tell\n  the user the Content action surface was not available.\n\n## Action Examples\n\nPrefer JSON input for action calls:\n\n```bash\npnpm action list-documents\npnpm action get-document '{\"id\":\"document-id\"}'\npnpm action edit-document '{\"id\":\"document-id\",\"find\":\"old copy\",\"replace\":\"new copy\"}'\npnpm action update-document '{\"id\":\"document-id\",\"content\":\"# Updated\\n\\nBody\"}'\n```\n\nRun `refresh-list` after create/update/delete operations when you need the\nopen Content UI sidebar to repaint immediately.\n\n## Local Folder Sources\n\nInstall into an existing repo with:\n\n```bash\nnpx @agent-native/core@latest skills add content --mode local-files --scope project\n```\n\nThe installer copies this skill and writes or updates `agent-native.json` with\ndatabase-backed local-folder sources for `docs/`, `blog/`, `content/`, and\n`resources/`, plus a `components/` folder for local MDX components. A trusted\nlocal bridge imports these files into the workspace's canonical Files database.\nRun `sync-manifest-local-folder-source` with a root's generated\n`source.connectionId`, or launch `agent-native content local-files <target>`,\nto connect and pull it. A typical root looks like:\n\n```json\n{\n  \"version\": 1,\n  \"apps\": {\n    \"content\": {\n      \"roots\": [\n        {\n          \"name\": \"Docs\",\n          \"path\": \"docs\",\n          \"kind\": \"docs\",\n          \"extensions\": [\".md\", \".mdx\"],\n          \"source\": {\n            \"type\": \"local-folder\",\n            \"connectionId\": \"local-folder:<opaque-id>\",\n            \"truthPolicy\": \"source_primary\"\n          }\n        }\n      ],\n      \"components\": \"components\",\n      \"extensions\": \"extensions\",\n      \"hide\": [\"**/_*.md\", \"**/_*.mdx\"]\n    }\n  }\n}\n```\n\nLocal-folder synchronization does not make the host language model local, and\nthe hosted Content app cannot read private repo files by itself. File access\nrequires a local Content app, Agent-Native Desktop, or another trusted bridge.\n\n## MDX And Components\n\n- Preserve frontmatter keys you do not understand. Preserve MDX imports,\n  exports, JSX, and expression props unless the user explicitly asks to change\n  them.\n- Use local components from the configured `components` folder. Components\n  should be PascalCase exports from `.tsx` files; simple editable input metadata\n  can live next to them as `ComponentNameInputs`.\n- Use `list-local-component-files` and `write-local-component-file` for\n  component source changes when Content tools are available. Otherwise edit the\n  component files directly like normal repo source.\n\n## Boundaries\n\n- A database page and its source file can change independently. Use folder\n  check/pull/push and resolve reported conflicts rather than silently overwriting\n  either revision.\n- Do not push/pull Notion, Builder.io, or other provider-backed content unless\n  the user explicitly asks for provider sync.\n- Do not paste secrets, private provider data, or credential-looking values into\n  docs, generated pages, frontmatter, examples, or local components.\n";