Nm Leyline Deferred Capture
v1.0.0>- Contract for unified deferred-item capture across plugins. Defines CLI interface, issue template, label taxonomy, and compliance test
⭐ 0· 44·1 current·1 all-time
by@athola
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The SKILL.md is a specification for implementing a deferred-capture CLI and issue template. The stated purpose matches the content (CLI args, issue format, labels, duplicate-detection, and a compliance test).
Instruction Scope
The instructions reference runtime behaviors and external commands (gh issue list, current git branch, python3 scripts/deferred_capture.py) and environment usage (fallback to $CLAUDE_SESSION_ID, $HOME paths). This is reasonable for a developer contract, but the skill metadata doesn't declare required binaries or files even as optional; callers should not assume those tools/scripts exist.
Install Mechanism
There is no install spec and no code shipped with the skill (instruction-only). That aligns with a spec/contract; nothing is written to disk by the skill itself.
Credentials
The document references environment values (CLAUDE_SESSION_ID, $HOME) and filesystem paths, but the registry metadata lists no required environment variables or credentials. This is acceptable for an optional session-id source, but callers should be aware the implementation may read those env vars at runtime.
Persistence & Privilege
The skill is not always-on and does not request persistent privileges or modify other skill/system configs. Autonomous invocation is allowed (default) but not combined with any other concerning privileges.
Assessment
This SKILL.md is a specification meant for plugin authors rather than a runnable program. Before using or implementing it: 1) note that the doc assumes developer tools that are not declared — ensure your environment has git and the GitHub CLI (gh) and python3 if you run the compliance test; 2) the compliance command refers to scripts/deferred_capture.py, which is not provided here — verify your wrapper includes an appropriate script or adjust the test; 3) the spec may read $CLAUDE_SESSION_ID and $HOME paths at runtime — confirm you are comfortable with those environment reads and that no unexpected credentials are used; 4) when implementing the wrapper that calls gh, be mindful of GitHub CLI auth (tokens) and scopes — the spec does not request credentials itself, but a wrapper will need authenticated gh access to create/check issues. If you only want the contract text, no binaries or credentials are required.Like a lobster shell, security has layers — review code before you run it.
latestvk97fkrc34t72ezqpdk3kd65hq584s6x8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis