joelhooks/always-on-guidance
packages/opencode-swarm-plugin/claude-plugin/skills/always-on-guidance/SKILL.md
Always-on rule-oriented guidance for claude-plugin agents. Use to align behavior, tool usage, and model-specific defaults while avoiding deprecated bd/cass references. Related skills: swarm-coordination, testing-patterns.
$ install --global
skillsauthnpx skillsauth add joelhooks/swarm-tools always-on-guidanceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 6, 2026, 9:37 AM336.8s1 file scanned
SKILL.md
- name:
- always-on-guidance
- description:
- |
- Related skills:
- swarm-coordination, testing-patterns.
Always-On Guidance
Global Rules
- Follow instruction priority: system → developer → user → AGENTS.
- Use swarm plugin tools (
hive_*,swarm_*,swarmmail_*,hivemind_*); avoid deprecatedbd/cassreferences. - Stay within assigned files; reserve before edits with
ttl_seconds; release reservations on done; finish swarm work withswarm_complete. - After every
swarm_spawn_subtask, immediately callTask(subagent_type="swarm-worker", prompt="<prompt returned by swarm_spawn_subtask>"). swarmmail_release_allis coordinator-only for stale/orphaned reservations.- Keep outputs concise and action-oriented.
Model Defaults
GPT-5.2-code
- Prefer strict checklists and short imperatives.
- Ask a single clarifying question if blocked; otherwise proceed.
- Avoid speculative reasoning; state decisions plainly.
- Keep outputs minimal and non-narrative.
Opus 4.5
- Allow brief rationale (1–2 sentences) for decisions.
- Use sections when work has multiple phases.
- Suggest alternatives only when risk is high, then choose one.
- Stay compact; avoid long exposition.
Testing Discipline
- Use red → green → refactor when tests cover the touched area.
- If tests are absent or out of scope, state that explicitly.
Related Skills
joelhooks/testing-patterns
development
VerifiedTrustedCommunity
Patterns for testing code effectively. Use when breaking dependencies for testability, adding tests to existing code, understanding unfamiliar code through characterization tests, or deciding how to structure tests. Covers seams, dependency injection, test doubles, and safe refactoring techniques from Michael Feathers.
613SKILL.mdUpdated Apr 6, 2026
joelhooks/system-design
tools
VerifiedTrustedCommunity
Principles for building reusable coding systems. Use when designing modules, APIs, CLIs, or any code meant to be used by others. Based on "A Philosophy of Software Design" by John Ousterhout. Covers deep modules, complexity management, and design red flags.
613SKILL.mdUpdated Apr 6, 2026
joelhooks/swarm-coordination
development
VerifiedTrustedCommunity
Multi-agent coordination patterns for OpenCode swarm workflows. Use when working on complex tasks that benefit from parallelization, when coordinating multiple agents, or when managing task decomposition. Do NOT use for simple single-agent tasks.
613SKILL.mdUpdated Apr 6, 2026
joelhooks/skill-generator
development
VerifiedTrustedCommunity
Meta-skill for generating new skills with proper format and structure. Use when creating new skills for the swarm system or when agents need to generate skill scaffolds. Ensures skills follow conventions (frontmatter format, directory structure, bundled resources).
613SKILL.mdUpdated Apr 6, 2026