Menü
Use when asked to ingest a URL or existing kb/sources snapshot into a .ingest.md source analysis.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | cp-skill-ingest |
| description | Use when asked to ingest a URL or existing kb/sources snapshot into a .ingest.md source analysis. |
| type | kb/types/instruction.md |
| user-invocable | true |
| allowed-tools | Read, Write, Grep, Glob, Bash, Skill |
| context | fork |
| model | opus |
| argument-hint | [url-or-file] — URL (https://...) or path to .md file in kb/sources/. No argument lists recent snapshots. |
Ingest one source into a kb/sources/*.ingest.md report. The source may be a
URL or an existing Markdown snapshot under kb/sources/.
Target: $ARGUMENTS
The direct output is the .ingest.md report next to the source snapshot. URL
snapshotting and connection discovery may write their own delegated artifacts.
Do not directly write any other library artifacts.
Interpret "our" through the installed KB's goals and local collection contracts. In this repository, "our" means agent-operated KB methodology. In another installed KB, it means that project's declared system, work, codebase, policy, product, or domain.
Read and follow kb/sources/types/ingest-report.md before drafting the report.
If this skill and the type spec conflict about report content, the type spec
wins.
Resolve the target.
$ARGUMENTS is empty, list recent kb/sources/*.md files excluding
.json and .ingest.md, then ask which one to ingest.http:// or https://, invoke
cp-skill-snapshot-web on the URL. Parse the Snapshot saved: line from
its output; that path is the source snapshot for the next step.Run connection discovery.
Invoke cp-skill-connect on the source snapshot path. Wait for it to finish.
For source snapshots, read
kb/reports/connect/sources/<snapshot-name>.connect.md.
Extract connection context. From the generated connect report, note:
Treat Maintenance Observations as non-actionable context: mention durable
signals in the ingest report only when relevant, and do not act on or promote
them during ingest.
The connect report is generated, gitignored working context. Do not cite it, link to it, or name its path in the durable ingest report. Summarize its findings and link only durable KB artifacts or source snapshots.
Select, do not transcribe: connect casts a wide candidate net by design.
Drop weak, speculative, or duplicate edges and keep only settled, durable
judgments about this source's role. Write Connections Found as compact
prose naming that role (for example: anchor, technical basis, counterpoint,
legal disposition, public statement, limitation) rather than an inventory of
every candidate connect surfaced.
If no casebook notes exist yet for the target collection, say so plainly and stop there. Do not substitute a full map of this source's relationships to other already-captured sources, and do not frame the section as prospective connections for notes that do not exist yet — that framing goes stale the moment notes are written, and re-deriving those relationships is connect's job to do then, not the ingest's job to pre-write now. A single relationship that bears on this source's likely role is enough.
Draft the ingest report.
Write the analysis as an ingest-report, using the source snapshot and the
connection context. The report must classify the source, summarize it,
explain how it connects to the current KB, extract goal-relative value, state
limitations, and recommend one advisory next action.
If the source is not relevant to this KB, say so in the report. Keep the report short, explain the mismatch, and recommend no promotion or source-only filing as appropriate.
Save the report next to the snapshot.
kb/sources/some-article.mdkb/sources/some-article.ingest.mdValidate. Run:
commonplace-validate kb/sources/some-article.ingest.md
If this run created or edited the source snapshot, validate that snapshot too. Fix validation failures in files this skill is allowed to write before stopping.
Report the result. Tell the user where the ingest report was saved and state the recommended next action.
cp-skill-connect before classification or value extraction..ingest.md report directly.Write a single KB note — apply the target collection's conventions and path-valued type-spec, commit only in-hand links plus a cheap duplicate check, validate, then hand graph discovery to cp-skill-connect.
Discover connections for a single artifact. Writes a connect-report under kb/reports/connect/<collection>/ without mutating library artifacts or indexes. Use with an artifact path or artifact name.
Write or update a local code-grounded agent memory system review from a GitHub repository reference, including checkout refresh, optional sub-agent drafting, semantic QA, and validation.
Snapshot any URL into kb/sources/. Routes by URL type — GitHub issues/PRs via gh API, X/Twitter via xdk, PDFs via download+Read, web pages via WebFetch. One skill, URL in, markdown snapshot out. Triggers on "/cp-skill-snapshot-web", "/cp-skill-snapshot-web [url]".
Convert notes between types. Currently supports text to note by adding unverified structured frontmatter, renaming the file to match the title, and fixing backlinks. Use with a note path or note name.
Experimental: revise a note with an AutoReason-style loop using fresh Codex sub-agents for critic, revision, synthesis, and blind judging. Keep the incumbent, generate a critique-driven revision and synthesis, then use blind Borda judging to decide whether to continue. Triggers on "/cp-skill-revise-autoreason [note]".