Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/deferred-capture
Defines the contract for deferred-item capture across plugins.
Passed 18 of 20 test cases with the skill, and 8 of 20 without it.
and 22 more in the full report
12 fixed9 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the markdown metadata block of a deferred issue, what specific metadata fields must appear under the Deferred Item section?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the Captured by field in the issue body metadata. | Missed | Passed |
The instructions your model reads when the skill loads.
plugins/<plugin>/scripts/deferred_capture.py)Specification that all plugin deferred-capture wrappers implement. Not a runtime dependency, just a convention.
Required arguments:
--title (str): Concise description. Becomes issue title
after [Deferred] prefix--source (str): Origin skill. One of: war-room, brainstorm,
scope-guard, feature-review, review, regression, egregore--context (str): Why raised and why deferredOptional arguments:
--labels (str): Comma-separated additional labels beyond
deferred and source--session-id (str): Session ID. Canonical source:
session_id from the hook payload stdin
(jq -r '.session_id'), fallback: UTC timestamp
YYYYMMDD-HHMMSS--artifact-path (str): Absolute path or $HOME-based
path to source artifact--captured-by (str): explicit (default) or safety-net--dry-run (flag): Print JSON output without creating issuetest cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.