skillnet 0.6.0

Manage canonical AI skill stores, derived views, and calibration data for multi-phase-plan.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94

# Hook ingestion

`skillnet hook ingest` records Claude Code hook payloads into the
`skill_invocations` table. This captures every configured skill invocation as
it happens, without requiring a later `skillnet calibration record` pass and
without mixing raw hook events into the multi-phase-plan calibration tables.

## Quick start

1. Install the binary:

   ```sh
   cargo install skillnet
   ```

2. Point skillnet at your calibration database. For Postgres, set one of the
   supported URL variables:

   ```sh
   export DATABASE_URL='postgres://skillnet@localhost/skillnet'
   ```

   For SQLite, select the runtime data directory instead:

   ```sh
   export SKILLNET_DATA_DIR="$HOME/.local/share/skillnet"
   ```

3. Install the Claude Code hook entries and confirm status:

   ```sh
   skillnet hook install
   skillnet hook status
   ```

4. Run any Claude Code skill, then inspect recent rows:

   ```sh
   psql "$DATABASE_URL" -c \
     'select skill_name, hook_event, started_at from skill_invocations order by id desc limit 5;'
   ```

## Managed entries

`skillnet hook install` edits only the selected Claude Code settings file,
defaulting to `$HOME/.claude/settings.json`. It preserves unrelated settings
and hook entries, creates a one-time `.bak` next to an existing settings file,
and writes through a temporary file before renaming.

Managed hook entries are marked with `_skillnet_managed: true`. Re-running
`skillnet hook install` removes previous skillnet-managed entries for the
selected events, then writes fresh entries. That makes the command idempotent
and safe to run from provisioning tools.

To remove only skillnet-managed entries:

```sh
skillnet hook uninstall
```

## Home Manager

The Home Manager module can run the same install command during activation:

```nix
programs.skillnet = {
  enable = true;
  hooks = {
    enable = true;
    events = [ "PostToolUse" ];
    matchers = [ "Skill" ];
    settingsFile = "${config.home.homeDirectory}/.claude/settings.json";
  };
};
```

The activation hook runs after `writeBoundary` and is prefixed with
`$DRY_RUN_CMD`, so `home-manager switch --dry-run` does not mutate the settings
file. Setting `programs.skillnet.hooks.enable = false` later does not
auto-uninstall existing managed entries; run `skillnet hook uninstall`
explicitly when you want removal.

## Troubleshooting

- `skillnet hook ingest` is designed for Claude Code hook execution. Without
  `--strict`, database and payload errors are printed to stderr and the command
  exits 0 so a broken logging path does not break interactive tool use.
- Use `skillnet hook ingest --strict --event PostToolUse` in tests and CI when
  failures should be fatal.
- If `skillnet hook install` reports a JSON parse error, clean up comments or
  invalid JSON in the settings file first. The command refuses to rewrite
  invalid JSON rather than risk dropping user content.
- If `skillnet hook status` prints `not installed`, run `skillnet hook install`
  against the same `--settings` path that Claude Code reads.