agent-ks-docslisted

Use this skill for ANY non-tracker content work in an agent-knowledge-system project — writing markdown, creating blog posts, editing docs pages, configuring site.yaml / navbar.yaml / footer.yaml / .env, themes, image optimization, and anything touching files under the project's `data/` folder EXCEPT the issue tracker. The skill triages the task to a domain-specific reference file (writing, docs-layout, blog-layout, settings-layout, images). TRIGGER eagerly — documentation work in this project almost always benefits from this skill. Use it whenever the user mentions docs, frontmatter, settings.json, blog posts, the data folder, content types, or themes. For the issue tracker (data/todo/ — issues, subtasks, comments, brainstorms, agent-logs, the dump) use the agent-ks-issues skill instead. SKIP only for pure framework source-code work under `astro-doc-code/src/` that doesn't touch any documentation file.
sidhanthapoddar99/agent-knowledge-system · ★ 0 · Data & Documents · score 70

Install: claude install-skill sidhanthapoddar99/agent-knowledge-system

# Documentation skill Operating manual for working in an agent-knowledge-system project (Astro-based engine). The project's content + config live under the user's `data/` and `config/` folders and render through Astro layouts shipped inside the `agent-knowledge-system/` framework folder. The framework's *own* bundled docs (the canonical user-guide for the framework itself) live at `agent-knowledge-system/default-docs/data/user-guide/` — read those when this skill is unclear. > **Two modes.** *Consumer mode* (the default) — the framework is a subfolder of the user's project (`<project>/agent-knowledge-system/`) and the user's content lives at the project root (`config/`, `data/`, `assets/`, `themes/` next to the framework folder). *Dogfood mode* — the framework repo *is* the project; content lives under `default-docs/`. The scripts derive the actual location from `.env` (`CONFIG_DIR`), so this skill describes paths relative to **the user's content folders** and the underlying scripts handle both modes. Where this skill says `data/`, the script resolves to `<project>/data/` (consumer) or `<framework>/default-docs/data/` (dogfood). > **Sibling skill — `agent-ks-issues`.** This plugin also ships a self-contained `agent-ks-issues` skill that owns the **entire issue-tracker domain** — issues, subtasks, comments, brainstorms, notes, agent-logs, agent-memory, the tracker vocabulary, the issues dump, and the execution verbs (audit / refactor / loop / discuss) against a tracked issu