@falkenslab/agent-kit 0.17.0 → 0.18.0

package/assets/knowledge-plugin-files/skills/knowledge-lint/SKILL.md

@@ -1,26 +0,0 @@
----
-name: knowledge-lint
-description: Health-check the knowledge base - broken links, pages missing from index.md, orphan pages, one-way links, duplicated concepts, mentioned-but-missing concepts, contradictions, gaps - fix what's mechanical and report the rest.
----
-
-# Linting the knowledge base
-
-A knowledge base maintained across sessions drifts: links break, pages go unlisted, the same concept appears under two names. Lint it when asked and after a large ingest. Load `knowledge-pages` first for the templates.
-
-## Checks
-
-Use `Glob` to list pages and `Grep` (always with `path` inside the knowledge base) to find links, instead of reading every page in full.
-
-1. **Broken links**: a relative link whose target file doesn't exist. Fix it if the right target is obvious (a typo, a page under a close name); otherwise report it.
-2. **Index**: every page is listed in `index.md` and every entry there points to an existing page. Fix it.
-3. **Orphans**: pages nothing links to (`Grep` for the file name). Link them from where they belong, or report why they don't belong anywhere.
-4. **One-way links**: a summary that feeds a concept which doesn't list it back... Add the missing side.
-5. **Duplicates**: two pages for the same idea under different names. Merge the content into one, mark the other as superseded (never delete it) and repoint links.
-6. **Missing pages**: terms that several pages treat as concepts or entities but have no page. Create them if the material is there; otherwise list them.
-7. **Contradictions**: claims that disagree across pages without being recorded as such. Record both sides, attributed.
-8. **Provenance**: claims with no traceable source. Add the link, or mark them as unsourced.
-9. **Gaps**: originals `list_sources` reports as new (no summary yet), changed (their summary may be stale) or missing (deleted by hand: their summaries point nowhere), and concepts mentioned but never explained by any source. Report them - they are what to ingest, update or find next.
-
-## Close
-
-Append `## [date] lint | <summary>` to `log.md` listing what was fixed. Then report to the human: what you fixed, and what needs their decision or more material. Don't make judgement calls silently - merging pages that are only similar, or choosing between contradictory sources, goes in the report.

package/assets/knowledge-plugin-files/skills/knowledge-pages/SKILL.md

@@ -1,137 +0,0 @@
----
-name: knowledge-pages
-description: Exact templates and conventions for every page of the knowledge base (index, log, overview, summary, concept, entity and synthesis pages) - load it before creating a knowledge base page or restructuring one, so every page keeps the same shape and links.
----
-
-# Knowledge base page templates
-
-The knowledge base's layout and rules are in the system prompt ("Knowledge base"). This skill only adds the exact shape of each page. Headings and frontmatter keys stay in English (they are structure); the text under them is in the human's language. Dates are `YYYY-MM-DD`. Links are relative markdown links (from `concepts/x.md`, a summary is `../summaries/y.md`; an original file is `../../sources/...`, adjusted to where the folders really are).
-
-Every page starts with YAML frontmatter; `updated` changes whenever you edit the page.
-
-## index.md
-
-The catalog and entry point. One line per page, grouped by section: Summaries, Concepts, Entities, Syntheses (plus any section the domain adds).
-
-```markdown
-# Index
-
-## Summaries
-- [Q3 architecture review](summaries/q3-architecture-review.md) - decisions taken on the billing service
-## Concepts
-- [Idempotency](concepts/idempotency.md) - safe retries of a request
-```
-
-## log.md
-
-Append-only; never edit past entries. Newest at the bottom.
-
-```markdown
-## [2026-10-03] ingest | Q3 architecture review
-- created: summaries/q3-architecture-review.md, concepts/idempotency.md
-- updated: entities/billing-service.md, index.md
-```
-
-## overview.md
-
-A living synthesis of the whole knowledge base, rewritten (not appended) as understanding grows: what it covers, its main blocks and how they connect (with links), what is still unknown.
-
-## Summary page (`summaries/<slug>.md`)
-
-One per ingested source.
-
-```markdown
----
-type: summary
-title: "<Title>"
-file: <relative link to the original in sources/, if any>
-url: <original URL, if any>
-ingested: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-
-# <Title>
-
-## Summary
-<Two to four paragraphs: what it actually says.>
-
-## Key points
-- Claims, definitions or figures likely to be needed later, quoted literally when exact wording matters.
-
-## Pages it feeds
-- [Concept or entity](../concepts/<slug>.md)
-
-## New or surprising
-- What this source adds to what the knowledge base already had.
-
-## Contradictions
-- Conflicts with other pages, linked.
-```
-
-## Concept page (`concepts/<slug>.md`)
-
-One idea per page.
-
-```markdown
----
-type: concept
-aliases: []
-updated: YYYY-MM-DD
----
-
-# <Concept>
-
-<Definition in one or two sentences.>
-
-## Explanation
-<How it works, at the depth the sources give.>
-
-## Connections
-- Requires: [Concept](<slug>.md)
-- Related: [Concept](<slug>.md) - how
-
-## Sources
-- [Summary](../summaries/<slug>.md) - what it says about this
-
-## Contradictions and open questions
-- "<Source A> says X; <source B> says Y" - both attributed.
-```
-
-## Entity page (`entities/<slug>.md`)
-
-A concrete thing: a system, a component, an organization, a document, a person only when they are a public role rather than private individual details.
-
-```markdown
----
-type: entity
-kind: <system | component | organization | document | other>
-aliases: []
-updated: YYYY-MM-DD
----
-
-# <Name>
-
-<What it is, one or two sentences.>
-
-## Facts
-- Attributed facts, each linking the summary or source it comes from.
-
-## Connections
-- [Concept or entity](../concepts/<slug>.md) - how
-```
-
-## Synthesis page (`syntheses/<slug>.md`)
-
-An answer worth keeping: a comparison, an analysis, a report.
-
-```markdown
----
-type: synthesis
-question: "<The question it answers>"
-updated: YYYY-MM-DD
----
-
-# <Title>
-
-<The answer, with links to every page it draws on.>
-```

package/assets/knowledge-plugin-files/skills/knowledge-query/SKILL.md

@@ -1,14 +0,0 @@
----
-name: knowledge-query
-description: Answer a question from the knowledge base - find the relevant pages through the index, read them, answer with links to them, and file the answer back as a synthesis page when it is worth keeping.
----
-
-# Querying the knowledge base
-
-The knowledge base exists so a question doesn't start from zero. Answer from it first; go back to the originals or the web only for what it doesn't hold.
-
-1. **Start from the index.** Read `index.md`, pick the pages that can matter, read those (not the whole knowledge base). `Grep` inside the knowledge base for terms and aliases the index doesn't reveal.
-2. **Answer from the pages**, linking each one you drew on. Say what comes from the knowledge base, what comes from an original in the sources folder (read it if the knowledge base is thin or contradictory) and what comes from outside (label it as such).
-3. **Say what is missing.** If the knowledge base can't answer part of the question, say so and name the source that would fill it, instead of filling the gap from memory silently.
-4. **File it back.** If the answer is a comparison, an analysis or a report that will be asked again, save it as `syntheses/<slug>.md` (template in `knowledge-pages`) with links to its inputs, add it to `index.md`, and log it: `## [date] query | <question>`. A quick factual answer needs no page.
-5. **Feed the knowledge base.** If answering revealed a concept or fact that has no page, or a contradiction, fix that in the knowledge base too and log it.