agentleFS
iwesysiwesys/IWE/.claude/skills/ke/SKILL.md

ke

Skill0 starsChanged 25 days agoMITView on GitHub

Knowledge Extraction — captures and routes knowledge at work boundaries.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Does not process extraction-reports/*.md (pending-review candidates from agent R2).

    line 25
  2. Very specific:

    Does not write Pack entities (files DP.*, PD.*, MIM.*).

    line 26
  3. Very specific:

    Does not launch the extractor agent R2 (runs via launchd every 3h during work hours, invoked as extractor.sh inbox-check).

    line 27
  4. Distinctive:

    Test HD #29: *"If we replace the vendor, does the statement become false?"*

    line 53
  5. Distinctive:

    If "Immediately" → record right away

    line 59
  6. Very specific:

    If "Close" → append an entry to inbox/captures/<YYYY-MM>.md:

    line 60
  7. Very specific:

    If this is a Distinction — propose a formulation for memory/hard-distinctions.md.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Knowledge Extraction (Capture-to-Pack)

Execute knowledge extraction: $ARGUMENTS

Scope

This Skill does:

  • Inline capture at a Session boundary (routing "what → where", announcing "Capture: X → Y").
  • Immediate rule recording (1–3 lines) to CLAUDE.md.
  • Deferred recording (complex knowledge) — appending to inbox/captures/<YYYY-MM>.md (routed by event date; rule → Step 3) for the extractor agent. The legacy file inbox/captures.md does not receive new entries (rotation WP-526, 29.08.2026) — treat it as an archive.

This Skill does NOT do:

  • Does not process extraction-reports/*.md (pending-review candidates from agent R2). That is handled by /apply-captures.
  • Does not write Pack entities (files DP., PD., MIM.*). That is handled by /apply-captures after an R15 decision. Alternatively, R15 can write to the Pack directly via Edit — /apply-captures is not the only path.
  • Does not launch the extractor agent R2 (runs via launchd every 3h during work hours, invoked as extractor.sh inbox-check).

Three knowledge tools (distinctions):

ToolRoleWhenOutput
/ke (this Skill)R14 Client / R1 StrategistSession boundary, inlineRule in CLAUDE.md / entry in inbox/captures/<YYYY-MM>.md
extractor.sh inbox-check (agent R2)R2 Extractor (AI, launchd 3h, work hours)Automaticallyextraction-reports/*.md with status: pending-review
/apply-capturesR15 ValidatorClose when N>0 pending-reviewPack entities + commit + status update

Detailed VDV cycle map: <governance-repo>/inbox/WP-247-ke-pipeline-vdv.md

Step 1. Identify the knowledge type

TypeDestinationWhenVia KE?
Rule for all repos (1–3 lines)CLAUDE.md (workspace root)ImmediatelyNo
Rule for a single repo (1–3 lines)<repo>/CLAUDE.mdImmediatelyNo
Domain (architecture, patterns)Corresponding PackCloseYes
Distinction, Method, FM, WPCorresponding PackCloseYes
Implementation (vendor, stack, deployment)DS docs/CloseYes (KE → DS)
Major lessonmemory/<topic>.mdCloseNo
Post seed{{GOVERNANCE_REPO}}/drafts/draft-list.mdCloseNo

Step 2. Routing

Test HD #29: "If we replace the vendor, does the statement become false?"

  • Yes → implementation (DS)
  • No → domain (Pack)

Step 3. Recording

  • If "Immediately" → record right away
  • If "Close" → append an entry to inbox/captures/<YYYY-MM>.md:
    • unambiguous event date in the entry → month of the event;
    • event date is absent or ambiguous → month of recording (today), mark in the entry text as event_date: unknown or event_date: ambiguous — do not guess
    • inbox/captures.md (legacy) — read-only, do not add new entries there

Step 4. Announce

Output: "Capture: [what] → [where]"

If this is a Distinction — propose a formulation for memory/hard-distinctions.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.