Shell engineering
shell engineering guidance for structured Harness Forge language packs.From its SKILL.md
npx -y skills add ldilov/harness-forge --skill shell-engineeringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 232 tokens by cl100k_base, as published. Nobody here has run it
Shell Engineering
Use this skill when the repository is primarily shell automation or when the task touches shell scripts.
Activation
- shell scripts dominate the task or repository
- the work touches automation, bootstrap, CI, or operational workflows
Load Order
rules/common/rules/shell/knowledge-bases/structured/shell/docs/knowledge-bases/structured/shell/examples/
Execution Contract
- inspect execution context, portability, and failure handling assumptions
- select the common and shell-specific rules for the change
- implement with explicit quoting, safety, and destructive-operation boundaries
- verify with the safest repo script path and the structured checklist
Outputs
- touched-script summary
- implementation summary
- validation result or blocker note
Validation
- run the script in dry-run or non-destructive mode when possible
- consult
knowledge-bases/structured/shell/docs/review-checklist.md
Escalation
- escalate when portability or destructive operations make the risk non-local
- escalate when shell compatibility cannot be confirmed safely
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.