Agent Skills: bash-script-helper
Expert helper for bash scripting, debugging, and best practices
ID: jackspace/ClaudeSkillz/bash-script-helper
166
Install this agent skill to your local
Skill Files
The files that make up bash-script-helper.
More agent skills
- plan-updateUse when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.
- apply-anthropic-skill-best-practicesComprehensive guide for skill development based on Anthropic's official best practices - use for complex skills requiring detailed structure
- research-assistantConduct thorough research on topics by searching the vault and synthesizing findings. Use when the user asks to research a topic, dig into something across notes, or wants a synthesis of what the vault knows about a subject.
- relay-clientSubscription and filter-assembly patterns for the Amethyst relay client layer in `commons/.../relayClient/`. Use when working with compose-scoped subscriptions (`ComposeSubscriptionManager`, `Subscribable`), filter assemblers (`MetadataFilterAssembler`, `ReactionsFilterAssembler`, `FeedMetadataCoordinator`), preloaders (`MetadataPreloader`, `MetadataRateLimiter`), EOSE managers, or any feature that needs to talk to relays lifecycle-aware from a composable. Complements `nostr-expert` (protocol filter syntax) and `kotlin-coroutines` (callbackFlow patterns).
- fuzzing-dictionaryBuilds and applies fuzzing dictionaries so a fuzzer can produce the keywords, magic bytes, and tokens a target expects. Covers extracting tokens from source, headers, binaries, and specifications, dictionary syntax, and wiring one into libFuzzer or AFL++. Use when fuzzing a parser, protocol, or file format, when coverage stalls at input validation, or when a target compares against fixed strings.
- file-crdb-issueUse when filing, creating, or reporting GitHub issues for CockroachDB. Use when asked to open a bug report, feature request, investigation issue, or performance inquiry. Also use when the user mentions wanting to track a problem, report a regression, or document unexpected behavior in CockroachDB.