alexion/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move grill artifacts outside project repos

Browse Source
This commit is contained in:
alexion
2026-07-30 00:05:59 -04:00
parent b541251f98
commit 5886017976
6 changed files with 8 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
.agents/CONTEXT.md
View File

@@ -1,58 +0,0 @@
# Skills
A personal collection of agent skills packaged through Nix.
The language below covers the knowledge-mining pipeline — the `consume` (write) and `wiki` (read) pair that move knowledge into and out of the user's Obsidian vault.
## Language
### Places
**Vault**:
The user's personal Obsidian knowledge base, read through `wiki` and written only within one area by `consume`.
_Avoid_: notes folder, Obsidian
**Pull channel**:
The vault area holding reusable knowledge, retrieved on demand by a future agent that goes looking for it.
_Avoid_: wiki proper, retrieval store
**Push channel**:
The target's own always-loaded documentation (`AGENTS.md`), whose value is being in front of an agent unprompted.
_Avoid_: proactive store, always-on docs, `CLAUDE.md`
**Target**:
The single source `consume` ingests in one run — currently a project directory.
_Avoid_: source (reserve for the raw material within the target), input
**Compatibility surface**:
A legacy harness-specific file or directory that points an older agent harness to the canonical agent-neutral surface.
_Avoid_: duplicate source, mirror
### Acceptance axes
**Generalizes**:
A mined fact's property of teaching something true on a *different* target, not only the one it came from.
_Avoid_: reusable, transferable (use only informally)
**Trigger-able**:
A mined fact's property of having a recognizable symptom, error, or task that would send a future agent to retrieve it.
_Avoid_: searchable, useful
### What a source line yields
**General lesson**:
The transferable principle split out of a source line.
_Avoid_: concept, insight
**Specific residue**:
The concrete, target-only answer left after the general lesson is split off.
_Avoid_: leftover, detail
**Proactive rule**:
A mined fact that generalizes but is not trigger-able — a verification-discipline or design-stance rule whose value is firing unprompted.
_Avoid_: habit, guideline
### Planning
**Contribution map**:
The many-to-many record of which consumed file fed which planned note, with the exact contributing sections, including files that fed nothing.
_Avoid_: provenance table, coverage map

17
.agents/adr/0001-consume-writes-target-push-channel.md
View File

@@ -1,17 +0,0 @@
# Consume writes the target's push channel, not only the vault
`consume` was scoped to write only inside the vault's `01 sources/claude/` area.
A real run showed that most mined knowledge is not wiki-shaped — specific residue and proactive rules belong in the target's own always-loaded `AGENTS.md` — and dropping it lost real signal, while redoing the target-doc edits by hand after each run was toil.
We decided `consume` writes a second channel outside the vault, the target's `AGENTS.md`, rather than only planning those edits for the user to apply.
## Considered Options
- **Plan-only** — spell the target-doc edits out in the report and have the user apply them by hand.
Rejected: the whole value is not redoing what the run already worked out.
- **Auto-write both channels (chosen)** — apply the target edits too, but present them as a distinct, independently-approvable write-set under the one plan-approval gate, so a write outside the vault is never a surprise.
## Consequences
`consume`'s blast radius now includes files outside the vault and outside the spec/task scaffolding it deletes.
The plan-approval gate is what keeps that safe: the target write-set is approved separately from the vault write-set, and a declined target write-set degrades to flagged suggestions.
Destructive edits to `AGENTS.md` are gated on capture — an entry is removed or trimmed only when its general part is present in the wiki.

5
.agents/adr/0002-agent-neutral-project-surfaces.md
View File

@@ -1,5 +0,0 @@
# Agent-neutral project surfaces
This repository uses `AGENTS.md` and `.agents/` as the canonical project instruction, context, ADR, spec, task, and project-local skill surfaces.
Claude Code compatibility remains through `CLAUDE.md` and `.claude/` shims because existing harnesses and skills still discover those paths.
The compatibility surfaces are pointers, not duplicate sources of truth, so future agents have one canonical place to read and update.