{
  "markdown": "# Open Knowledge Skills\n\nAgent Skills published by [Open Knowledge](https://openknowledge.ai). Each skill teaches\nan agent one repeatable task, and every one of them is plain markdown you can read before\nyou install it.\n\n`skills/` is generated. The skills there are projected from the Open Knowledge source\ntree, so each skill directory's leaf name matches its `SKILL.md` frontmatter `name`.\nThe layout groups by role:\n\n- `skills/core/` holds the platform and meta skills.\n- `skills/starter-packs/<pack>/` holds one folder per starter pack: the pack's\n  orientation skill, its member skills as sibling directories, and a README\n  explaining how they interact.\n\n## Install\n\nAdd this repository as a Claude Code plugin marketplace, then install what you want:\n\n```bash\n/plugin marketplace add inkeep/open-knowledge-skills\n/plugin install open-knowledge@open-knowledge-skills\n```\n\n`open-knowledge` is the platform skill: it teaches an agent to read, search, link, and\nwrite markdown through Open Knowledge's MCP server. The rest are optional packs.\n\n## What's published here\n\nInstall a pack by name, the same way: `/plugin install <pack>@open-knowledge-skills`.\n\n### Core\n\n| Skill | What it does |\n| --- | --- |\n| `open-knowledge` | The runtime contract for working inside an Open Knowledge project: reading, searching, linking, and writing markdown through its MCP server. |\n| `open-knowledge-discovery` | What Open Knowledge is, how to install it on a repository, and how to share a project with collaborators. |\n| `open-knowledge-write-skill` | Authoring a new Agent Skill: the frontmatter contract, progressive-disclosure structure, and how to install it into your editors. |\n\n### Starter packs\n\nEach pack ships an orientation skill that explains how to work in that project shape. Some\nadd task skills alongside it.\n\n| Pack | Orientation skill | Also ships |\n| --- | --- | --- |\n| `software-lifecycle` | proposals to decisions to specs to postmortems | `frame-a-proposal`, `write-a-spec`, `record-a-decision`, `write-a-postmortem`, `review-a-design` |\n| `knowledge-base` | source-grounded research: sources to research to articles | `research-with-sources`, `consolidate-notes` |\n| `codebase-wiki` | an agent-authored, source-grounded wiki of the surrounding codebase | |\n| `personal-crm` | a typed-entity vault of people, companies, and meetings, each with a rewritable summary and an append-only timeline | |\n| `note-taking` | a flat notes folder plus a daily journal, for when you just want to write | |\n| `writing-workflow` | a three-stage drafting flow: ideas to drafts to published | |\n| `worldbuilding` | a fiction encyclopedia of characters, settings, factions, and lore | |\n| `okf-knowledge-base` | a knowledge base conformant with Google's Open Knowledge Format from the first commit | |\n\nThe task skills stand on their own. `write-a-spec` and `record-a-decision` do not need an\nOpen Knowledge project, or the rest of their pack, to be useful.\n\nYou can also copy any skill straight into your agent's skills folder\n(`.claude/skills/`, `.cursor/skills/`, `.codex/skills/`, or the vendor-neutral\n`.agents/skills/`). Open Knowledge can install and update them for you, and keeps their\nversion history.\n\n## Writing your own\n\n`template/SKILL.md.example` is a starting point. The field that matters most is\n`description`: it is a routing rule, not a title, and it is what both skills.sh and the\nhost agent match on to decide whether to load the skill at all.\n\nRead [CONTRIBUTING.md](./CONTRIBUTING.md) before opening a PR.\n\n## License\n\n[MIT](./LICENSE)\n",
  "bytes": 3558,
  "sha": "8dcc483ac1bf23a62237840b4fbbaa1524dd3dd4381448322149d896009d2dde",
  "repo_slug": "inkeep/open-knowledge-skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/skl_inkeep_open_knowledge_skills_open_knowle_16bd07e1/readme"
}