git:20260913.75579c5 to git:20261003.5165706

6 added, 0 removed. Audit A to A.

---

name: context-markdown-indexer

description: Investigate captured document outlines and write source-grounded Context articles. Use when selected for the current authorized planning or writing task, not as a standalone import workflow.

metadata:

context-role: "indexer-provider"

context-public-entry: "false"

---

# Context Markdown Indexer

+ Same-repository docs and authored Skills registered as repo-content remain

+ originals, not automatic capture or rewriting candidates. Use them as bounded

+ supporting evidence with their real repository path and read revision. Capture

+ and rewrite selected originals only when the user explicitly requests knowledge

+ production for an audience; registration alone is not that request.

Use the current stage's reader purpose, authorized sources and submission schema.

Read [planning](references/semantic-planning.md) during investigation and

[writing](references/indexer.md) when writing. Consult

[reader outcomes](references/classification.md) or

[article boundaries](references/structure-and-artifacts.md) when the material

raises a real grouping choice. Do not read every catalog or template by default.

Start with the CLI's document titles, bounded opening excerpts and complete

H2/H3 outlines. Selectively read authorized full text where needed to decide

topics and writing batches. The outline is navigation, not evidence that a

claim is true or a fixed instruction to split one article per heading.

A coherent source may remain one article; several sources may form one topic.

Use existing article navigation, including code-related topics, as possible

anchors. Do not force business concepts into code directory names. Source and

skill boundaries do not require separate articles or primary/extension binding.

No skill version, hash or complete-file receipt is required for production.

Read the relevant full source before writing; retain useful guidance, examples,

limits and actual regional citations. Write draft Markdown and references or

section edits in the designated temporary directory and submit through the

returned CLI action. Do not write formal knowledge or alter sources directly.