[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1ARMM9TC7HYV3VYN102SP":3,"skill-same:01M7C1ARMM9TC7HYV3VYN102SP":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7C1ARMM9TC7HYV3VYN102SP","kb-track-document-types",null,"Use at session start, to orient (\"what is this folder\", \"where do I start\"), and after creating, moving or deleting any non-code file.","SterlingJF\u002Fknowledge-mcp","SterlingJF","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62030094?v=4","01M7C1A0FHGQB68MJT1BA8WQ7K","Sterling Freeman","01M7C1A0GM4R2Q188D1SC0P46D",1,"MIT","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-track-document-types\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kb-track-document-types\ndescription: 'Use at session start, to orient (\"what is this folder\", \"where do I start\"), and after creating, moving or deleting any non-code file.'\n---\n\n# Track Document Types\n\n1. **Read the document-types file.** Read `.knowledge-bus\u002Fplugins\u002Fknowledge-mcp\u002Fdocument-types.yaml` at the root folder with your own tools.\n   If missing, read `.knowledge-bus\u002Fplugins\u002Fknowledge-mcp\u002Frecord.yaml` for migration.\n   Use an empty string when both files are missing.\n   Read conventions along every affected ancestor path at session start.\n   Send `conventions_files` as `kb-write-document` describes, including explicit absence markers.\n   Reuse each file digest while its text remains unchanged.\n2. **Compare the complete inventory.** Enumerate the whole root with your own tools, including nested knowledge-base folders and relevant attachments.\n   Stop after an incomplete listing or enumeration failure. Send a listing only after enumeration succeeds.\n   Call `kb_prepare_document_types` with:\n   - `location`: the root folder, as text.\n   - `record`: the text read in the previous step.\n   - `listing`: every file outside `.knowledge-bus\u002F`, with root-relative `path` values. Add a `fingerprint` when cheap to compute.\n   - `knowledge_bus_folders`: every folder containing `.knowledge-bus\u002F`, sent as `kb-write-document` describes.\n\n   Retain the initial `listing_changes` through classification and naming-value calls until the prepared record is saved.\n   Follow-up answers can omit `listing_changes`; keep the initial events for the session-start report.\n   Use `listing_changes` for observed events and `changed` for prepared entry changes.\n\n   **Prepare the session-start review.** Follow Choose document types below for arrivals and unresolved move destinations.\n   Read file content when the name and folder leave the document type unclear.\n   Follow `kb-write-document` to collect recorded naming values; keep missing titles, dates and numbers as questions.\n   Join each assessment by current path, universe spec and document type after choosing the type.\n   Keep candidate proposals conditional; several candidates give no single proposal.\n   Assess every typed arrival and external move, using conventions in effect at the current path and their provenance.\n   Without a convention, use peers within the applicable universe specs.\n   Explain `already_matches`, missing peers, incomplete evidence, occupied destinations and destination type conflicts.\n   List `values_needed` beside the affected file and ask for the missing values.\n   Preserve the original entry when an external move reaches a folder without the saved document type.\n   Resolve that conflict before preparing another move.\n   Combine saved `no_document_type` entries with the current listing and `to_settle` to list files that still need a document type.\n   Keep explicit no-document-type entries until the person requests another classification; avoid repeated classification questions.\n   Deduplicate unresolved files by current path and include their event labels.\n\n   **Show the session-start review.** Say: “Compared the current listing with the document-types file.”\n   An empty record establishes no arrival dates; describe the inventory as new to the record.\n   Claim “since the last session” only when the saved record establishes that baseline.\n   Give complete counts for new, moved, deleted and fingerprint-update events before showing files.\n   Order groups as new files, moved files, deleted files, fingerprint updates and unresolved files.\n   Sort each group by current root-relative path in Unicode code-point order; sort deletions by the former path.\n   Preview at most 50 distinct files across all groups, counting each unresolved file once.\n   State the number shown, the total and the number omitted, even when no file is omitted.\n   Keep the complete listing, event arrays and assessments; the cap limits the conversational preview alone.\n   Summarize fingerprint-only updates as counts unless the person asks for details.\n   A first fingerprint establishes a baseline; claim changed content only when earlier fingerprints establish a difference.\n   Retain classifications after content changes and review filing on request.\n   Show old paths, retained classifications and assessments beside moved files.\n   Report discovered link problems after external moves; claim link repairs only after verifying the repairs.\n   Describe basename fallback pairs as observed moves without claiming verified content identity.\n   Leave ambiguous move pairs as arrivals and deletions, and give deleted files no filing proposal.\n   Describe unsaved entry changes as prepared changes.\n   Obtain classification-save permission separately from move permission.\n   Route one accepted proposal through `kb_prepare_document_move` and several through `kb_prepare_document_moves`.\n   Before acceptance, show the complete selected move list, every affected document and every new folder, including rows omitted from the preview.\n   Follow the existing search, digest, application, recovery and edit-recording sequence in `kb-write-document`.\n   Report completed moves and verified repairs after application.\n\n3. **Update after each file change.** Keep the complete listing current after creates, moves, renames, edits and deletions. After each change, call `kb_prepare_document_types` with the same `location` and `knowledge_bus_folders`. Include `changes` and the current `record` or `record_digest`.\n   After saving `record`, send the returned `digest` as `record_digest` instead of `record` on the next call.\n   Follow any `note` in `changed`.\n4. **Review names and folders.** Resolve conventions separately for each document.\n   Keep peer evidence within the applicable universe specs. Report broken parent selections before proposing moves.\n   Show missing naming values beside each affected typed file.\n   Follow `kb-write-document` to collect values for a file under review. Show `filing` proposals beside typed files. Keep proposals conditional while choosing a document type.\n   Prepare accepted moves through the Names, folders and moves sequence in `kb-write-document` before changing files.\n   Save the prepared document-types text with the move and link repairs. Valid moves retain every classification field.\n   Resolve destination type conflicts explicitly, preserving the original entry while choosing another folder or changing universe specs separately.\n\n5. **Choose document types.** For each file in `to_settle`, follow `kb-write-document` to choose from `candidates`, as for `kb_get_document_type`.\n   If no candidate matches the file name, use `every_document_type` from the `scopes` item at the file's `scope` index.\n   Send each choice in `entries` with `path`, `universe_spec` and `document_type`. Set `set_by` to `agent`.\n   For an untyped file, set `no_document_type` to true instead of sending `universe_spec` and `document_type`.\n   Put the reader in `audience.value` when known.\n   Set `audience.status` to `confirmed` after the person confirms the reader, and to `guessed` otherwise.\n6. **Record corrections.** When the person names another document type, no document type, or another reader, send the corrected entry with `set_by` set to `person`.\n   Send `allowed_by` with `basis` set to `request` and the person's words in `text`.\n7. **Get permission to save.** Save only with the person's permission.\n   Send permission to `kb_prepare_document_types` as `allowed_by`, following the Edits section of `kb-write-document`.\n   Without permission, show the proposed entry changes and ask for permission to save.\n8. **Save the returned text.** If `record` is null, skip the save. Otherwise, repeat the file-reading step to get the current text before saving.\n   - If the digest of the current text equals `based_on`, save `record` immediately. Create missing folders with your own tools.\n   - If the text changed, call `kb_prepare_document_types` with the new text, the same `changes`, `entries` and `allowed_by`, and no `listing`.\n     If the first call sent `listing`, add the first returned `listing_changes` to `changes`.\n\n   For migration, save the converted `record` as `document-types.yaml`.\n   Delete `record.yaml` only with the person's permission.\n\n9. **Recheck on request.** When the person requests a recheck, set `recheck` to true. The tool preserves entries with `set_by: person`.\n   Choose a document type for each file in `to_settle`.\n   After an accepted convention change, refresh filing assessments on request.\n   Keep existing document paths until a proposal is accepted.\n   Keep convention changes separate from classification changes and document moves.\n10. **Keep entries in the document-types file.** Change entries through `kb_prepare_document_types` or the prepared document-types text from `kb_prepare_document_move` or `kb_prepare_document_moves`.\n    Keep document text out of the document-types file.\n\nFor requested starter conventions, follow Templates in `kb-write-document`.\nAt session start, read saved conventions without reapplying templates or replacing accepted patterns.\nKeep classification permission, configuration permission and move permission separate.\n\nFor many proposals, request a folder review through `filing_review` with a complete listing.\nFollow Many files at once in `kb-write-document` for changes, drops, acceptance and application.\nKeep unresolved classifications and missing naming values visible.\nSave the complete prepared document-types update with the accepted moves.\nAvoid intermediate tracking updates while files occupy temporary paths.\nRefresh the inventory after completion without replaying moves already represented by the prepared record.\n","# Track Document Types\n\n1. **Read the document-types file.** Read `.knowledge-bus\u002Fplugins\u002Fknowledge-mcp\u002Fdocument-types.yaml` at the root folder with your own tools.\n   If missing, read `.knowledge-bus\u002Fplugins\u002Fknowledge-mcp\u002Frecord.yaml` for migration.\n   Use an empty string when both files are missing.\n   Read conventions along every affected ancestor path at session start.\n   Send `conventions_files` as `kb-write-document` describes, including explicit absence markers.\n   Reuse each file digest while its text remains unchanged.\n2. **Compare the complete inventory.** Enumerate the whole root with your own tools, including nested knowledge-base folders and relevant attachments.\n   Stop after an incomplete listing or enumeration failure. Send a listing only after enumeration succeeds.\n   Call `kb_prepare_document_types` with:\n   - `location`: the root folder, as text.\n   - `record`: the text read in the previous step.\n   - `listing`: every file outside `.knowledge-bus\u002F`, with root-relative `path` values. Add a `fingerprint` when cheap to compute.\n   - `knowledge_bus_folders`: every folder containing `.knowledge-bus\u002F`, sent as `kb-write-document` describes.\n\n   Retain the initial `listing_changes` through classification and naming-value calls until the prepared record is saved.\n   Follow-up answers can omit `listing_changes`; keep the initial events for the session-start report.\n   Use `listing_changes` for observed events and `changed` for prepared entry changes.\n\n   **Prepare the session-start review.** Follow Choose document types below for arrivals and unresolved move destinations.\n   Read file content when the name and folder leave the document type unclear.\n   Follow `kb-write-document` to collect recorded naming values; keep missing titles, dates and numbers as questions.\n   Join each assessment by current path, universe spec and document type after choosing the type.\n   Keep candidate proposals conditional; several candidates give no single proposal.\n   Assess every typed arrival and external move, using conventions in effect at the current path and their provenance.\n   Without a convention, use peers within the applicable universe specs.\n   Explain `already_matches`, missing peers, incomplete evidence, occupied destinations and destination type conflicts.\n   List `values_needed` beside the affected file and ask for the missing values.\n   Preserve the original entry when an external move reaches a folder without the saved document type.\n   Resolve that conflict before preparing another move.\n   Combine saved `no_document_type` entries with the current listing and `to_settle` to list files that still need a document type.\n   Keep explicit no-document-type entries until the person requests another classification; avoid repeated classification questions.\n   Deduplicate unresolved files by current path and include their event labels.\n\n   **Show the session-start review.** Say: “Compared the current listing with the document-types file.”\n   An empty record establishes no arrival dates; describe the inventory as new to the record.\n   Claim “since the last session” only when the saved record establishes that baseline.\n   Give complete counts for new, moved, deleted and fingerprint-update events before showing files.\n   Order groups as new files, moved files, deleted files, fingerprint updates and unresolved files.\n   Sort each group by current root-relative path in Unicode code-point order; sort deletions by the former path.\n   Preview at most 50 distinct files across all groups, counting each unresolved file once.\n   State the number shown, the total and the number omitted, even when no file is omitted.\n   Keep the complete listing, event arrays and assessments; the cap limits the conversational preview alone.\n   Summarize fingerprint-only updates as counts unless the person asks for details.\n   A first fingerprint establishes a baseline; claim changed content only when earlier fingerprints establish a difference.\n   Retain classifications after content changes and review filing on request.\n   Show old paths, retained classifications and assessments beside moved files.\n   Report discovered link problems after external moves; claim link repairs only after verifying the repairs.\n   Describe basename fallback pairs as observed moves without claiming verified content identity.\n   Leave ambiguous move pairs as arrivals and deletions, and give deleted files no filing proposal.\n   Describe unsaved entry changes as prepared changes.\n   Obtain classification-save permission separately from move permission.\n   Route one accepted proposal through `kb_prepare_document_move` and several through `kb_prepare_document_moves`.\n   Before acceptance, show the complete selected move list, every affected document and every new folder, including rows omitted from the preview.\n   Follow the existing search, digest, application, recovery and edit-recording sequence in `kb-write-document`.\n   Report completed moves and verified repairs after application.\n\n3. **Update after each file change.** Keep the complete listing current after creates, moves, renames, edits and deletions. After each change, call `kb_prepare_document_types` with the same `location` and `knowledge_bus_folders`. Include `changes` and the current `record` or `record_digest`.\n   After saving `record`, send the returned `digest` as `record_digest` instead of `record` on the next call.\n   Follow any `note` in `changed`.\n4. **Review names and folders.** Resolve conventions separately for each document.\n   Keep peer evidence within the applicable universe specs. Report broken parent selections before proposing moves.\n   Show missing naming values beside each affected typed file.\n   Follow `kb-write-document` to collect values for a file under review. Show `filing` proposals beside typed files. Keep proposals conditional while choosing a document type.\n   Prepare accepted moves through the Names, folders and moves sequence in `kb-write-document` before changing files.\n   Save the prepared document-types text with the move and link repairs. Valid moves retain every classification field.\n   Resolve destination type conflicts explicitly, preserving the original entry while choosing another folder or changing universe specs separately.\n\n5. **Choose document types.** For each file in `to_settle`, follow `kb-write-document` to choose from `candidates`, as for `kb_get_document_type`.\n   If no candidate matches the file name, use `every_document_type` from the `scopes` item at the file's `scope` index.\n   Send each choice in `entries` with `path`, `universe_spec` and `document_type`. Set `set_by` to `agent`.\n   For an untyped file, set `no_document_type` to true instead of sending `universe_spec` and `document_type`.\n   Put the reader in `audience.value` when known.\n   Set `audience.status` to `confirmed` after the person confirms the reader, and to `guessed` otherwise.\n6. **Record corrections.** When the person names another document type, no document type, or another reader, send the corrected entry with `set_by` set to `person`.\n   Send `allowed_by` with `basis` set to `request` and the person's words in `text`.\n7. **Get permission to save.** Save only with the person's permission.\n   Send permission to `kb_prepare_document_types` as `allowed_by`, following the Edits section of `kb-write-document`.\n   Without permission, show the proposed entry changes and ask for permission to save.\n8. **Save the returned text.** If `record` is null, skip the save. Otherwise, repeat the file-reading step to get the current text before saving.\n   - If the digest of the current text equals `based_on`, save `record` immediately. Create missing folders with your own tools.\n   - If the text changed, call `kb_prepare_document_types` with the new text, the same `changes`, `entries` and `allowed_by`, and no `listing`.\n     If the first call sent `listing`, add the first returned `listing_changes` to `changes`.\n\n   For migration, save the converted `record` as `document-types.yaml`.\n   Delete `record.yaml` only with the person's permission.\n\n9. **Recheck on request.** When the person requests a recheck, set `recheck` to true. The tool preserves entries with `set_by: person`.\n   Choose a document type for each file in `to_settle`.\n   After an accepted convention change, refresh filing assessments on request.\n   Keep existing document paths until a proposal is accepted.\n   Keep convention changes separate from classification changes and document moves.\n10. **Keep entries in the document-types file.** Change entries through `kb_prepare_document_types` or the prepared document-types text from `kb_prepare_document_move` or `kb_prepare_document_moves`.\n    Keep document text out of the document-types file.\n\nFor requested starter conventions, follow Templates in `kb-write-document`.\nAt session start, read saved conventions without reapplying templates or replacing accepted patterns.\nKeep classification permission, configuration permission and move permission separate.\n\nFor many proposals, request a folder review through `filing_review` with a complete listing.\nFollow Many files at once in `kb-write-document` for changes, drops, acceptance and application.\nKeep unresolved classifications and missing naming values visible.\nSave the complete prepared document-types update with the accepted moves.\nAvoid intermediate tracking updates while files occupy temporary paths.\nRefresh the inventory after completion without replaying moves already represented by the prepared record.\n",{"name":5,"description":7},"main","cf185140ce76567727e4f48051deaa415a65bd0e","runtime\u002Fskills\u002Fkb-track-document-types",0,"https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp","https:\u002F\u002Fgithub.com\u002FSterlingJF","https:\u002F\u002Fsterlingfreeman.net\u002F","Professional hobbyist 💭💭💭 | \r\n💼 Technical Product | \r\n🎓 Computer Science","2026-11-15 03:37:12",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add SterlingJF\u002Fknowledge-mcp --skill kb-track-document-types",{"tool":39,"command":40},"bunx","bunx skills add SterlingJF\u002Fknowledge-mcp --skill kb-track-document-types",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SterlingJF\u002Fknowledge-mcp --skill kb-track-document-types","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-track-document-types\u002FSKILL.md",true,[],[48,55,63,71,79,86],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7C1B4ZH3YBQ69YHDBCEPJWG","kb-write-document","Use before you write, revise, move or rename any non-code file, or review a proposed change to one, wherever it lives: a knowledge base, a codebase's docs and records, or a local or remote drive, locally or through a connector. Covers \"review this change\", \"check this before I save\", \"is this right\", \"what changed\" and \"undo that\".","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-write-document\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7C1B0G06WYNDDGC3VAQ90S9","kb-uncover-question","Clarify a question a Knowledge Bus universe should declare, testing its purpose and overlap with existing questions.","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-uncover-question\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-uncover-question\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7C1AVP2WNEANQE2WSH77V8Y","kb-uncover-decision","Recover a decision's alternatives, constraints, authority, and reversal conditions when its record lacks context.","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-uncover-decision\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-uncover-decision\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7C1AM57JQPW73A921H1BYJF","kb-ingest","Map existing notes or documents into Knowledge Bus definitions and sourced answers, surfacing conflicts and gaps without changing source files.","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-ingest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-ingest\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7C1AEFSC4TEWPS0XX5FQTK8","kb-import-document","Use when the person brings in notes, a transcript or a document written elsewhere, to work it into their non-code files or import it as a new document.","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-import-document\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7C1ABJG6Q8BV5SMC3SPJ4JB","kb-explore","Inspect or explain a Knowledge Bus universe (a spec or set of definitions): what it covers and for whom; optionally create or open its offline Explorer.","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-explore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSterlingJF\u002Fknowledge-mcp\u002Fblob\u002Fmain\u002Fruntime\u002Fskills\u002Fkb-explore\u002FSKILL.md",[],[]]