tmk241/ink-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Align Ink skills with frozen delegation contracts

Browse Source
This commit is contained in:
tmk241
2026-08-12 01:05:49 +02:00
parent 8547d6ea33
commit f6d0efdfc0
4 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/audit-ink-cli/SKILL.md
+4 -4
View File
@@ -37,14 +37,14 @@ changes belong to Ink's repository authority and implementation workflow.
- A human/operator may invoke Ink outside the governed agent. Give a copyable
operator command only when the user asks and its public help contract is proven.
- Use user-provided runtime output as runtime evidence. Otherwise inspect the
installed artifact identity and a demonstrably matching checkout's requirements,
installed artifact identity and a demonstrably matching checkout's specification,
tests, public help text, and source; label those findings as contract/source
evidence rather than executed runtime proof.
- Global and project policy files explain only their contribution. Effective
authority also depends on all policy layers, pinned executable and contract
bytes, startup freezing, and session decisions.
- Treat handovers, READMEs, examples, hidden source branches, and remembered argv
as leads. Public help owns operator-facing commands; requirements own intended
as leads. Public help owns operator-facing commands; the specification owns intended
behavior; tests and source establish current checkout behavior.
Distinguish three surfaces explicitly:
@@ -71,7 +71,7 @@ the frozen `tool delegate` subject.
**source-confirmed**, **missing**, **stale claim**, or **not proven**.
4. For an operator action, explain that the user—not the hosted agent—must run it.
Do not inspect or mutate session state as a substitute.
5. For a missing capability, require Ink's requirements authority before source
5. For a missing capability, require Ink's specification authority before source
implementation. Do not model it as a new external executable merely to bypass
the host boundary.
@@ -93,7 +93,7 @@ the frozen `tool delegate` subject.
EVIDENCE: <runtime output, installed artifact, matching source, or limitation>
SURFACE: <operator CLI, model built-in, or admitted external command>
FINDING: <observed/source-confirmed/missing/stale/not proven>
ACTION: <operator step, requirements step, or none>
ACTION: <operator step, specification step, or none>
```
Positive smoke: “Does Ink have a sessions command, and why can’t you run it?”