tooling

Included with Lifetime

$97 forever

Creates and improves bun-based tools for skills — decides when a tool earns its place, scaffolds zero-dependency scripts with dual output, validates tool quality, and wires tools into SKILL.md decision trees. Use when adding a tool to a skill, improving an existing tool, deciding whether something should be a tool or inline instructions, or reviewing tool quality.

General

What this skill does

# Tool Creation

## Decision tree
- What are you doing?
- **Deciding whether to create a tool** -> read `references/when-to-create-tools.md`, apply the earning criteria
- **Creating a new tool for a skill** -> follow "Creating a tool" below
- **Improving an existing tool** -> what's wrong?
- **Output is hard to parse programmatically** -> add `--json` output mode per `references/tool-conventions.md`
- **Tool is a thin wrapper around a single command** -> it probably shouldn't be a tool. Inline the command in SKILL.md and delete the tool file
- **Tool lacks help text or error handling** -> fix per `references/tool-conventions.md`
- **Tool has external dependencies** -> rewrite using only bun built-ins and node stdlib
- **Wiring a tool into a skill** -> follow "Wiring into SKILL.md" below
- **Reviewing tool quality** -> check against `references/tool-conventions.md` "Quality checklist"

## Creating a tool

### 1. Validate the need
Before writing any code, confirm the tool passes at least one bar from `references/when-to-create-tools.md`. If it doesn't, put the command inline in SKILL.md instead.

### 2. Write the tool
Create `tools/<tool-name>.ts` following the conventions in `references/tool-conventions.md`. The structural patterns there reflect how tools in this repo are built — follow them for consistency.

Key principles:

- Zero external dependencies. Bun built-ins and node stdlib only.
- Dual output: human-readable by default, `--json` for programmatic consumption.
- Fail loudly: errors to stderr, non-zero exit codes, never silently swallow failures.
- Self-documenting: `--help` describes what the tool does, its arguments, and its options.

### 3. Validate
After writing:

1. Run the tool with `--help` to verify the help text is clear
2. Run against a real target to verify it produces correct output
3. Run with `--json` to verify structured output is valid JSON
4. Run with missing/bad arguments to verify it fails cleanly

## Wiring into SKILL.md
1. Add the tool to the appropriate decision tree branch — point to it from the action where it's useful
2. Reference it in the key references table at the bottom of SKILL.md
3. Don't duplicate the tool's logic in SKILL.md — just say when to run it and what to do with the output

## Key references
|File|What it covers|
|---|---|
|`references/when-to-create-tools.md`|Decision criteria for whether something should be a tool vs inline instructions|
|`references/tool-conventions.md`|Structural patterns, conventions, and quality checklist for building tools|

Files: 3

Size: 9.0 KB

Complexity: 30/100

Category: General

Source: https://github.com/lucasilverentand/skills/tree/main/plugins/skill-creation/skills/tooling

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts