opencode-skills-collection 4.0.0 → 4.0.2

package/bundled-skills/quit-sponsor/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: quit-sponsor
+description: "Helps an AI agent provide non-judgmental, evidence-informed quit-smoking support with user-consented tracking, craving check-ins, and escalation to human or clinical help. Not medical care."
+category: personal-development
+risk: safe
+source: community
+source_repo: metrox-eth/quit-sponsor
+source_type: community
+date_added: "2026-07-12"
+author: metrox-eth
+tags: [quit-smoking, smoking-cessation, health, habits, addiction-recovery, wellbeing, coaching]
+tools: [claude]
+license: "MIT"
+license_source: "https://github.com/metrox-eth/quit-sponsor/blob/main/LICENSE"
+---
+
+# Quit-sponsor
+
+## Overview
+
+Quit-sponsor helps an AI agent act as a consistent, non-judgmental companion while an adult works toward stopping smoking. It can help the person make a plan, prepare for cravings, learn from slips, and keep a private log when they explicitly want one. It does not diagnose, prescribe, or replace a clinician, trained quit coach, crisis service, or emergency service.
+
+This is a condensed adaptation of [metrox-eth/quit-sponsor](https://github.com/metrox-eth/quit-sponsor). Apply the safety rules in this file even if upstream wording differs. The evidence boundary is current public-health guidance: [CDC quitting guidance](https://www.cdc.gov/tobacco/about/how-to-quit.html), the [WHO tobacco cessation guideline](https://www.who.int/publications/i/item/9789240096431), and [NICE NG209](https://www.nice.org.uk/guidance/ng209/chapter/treating-tobacco-dependence). These sources support behavioural help, quit planning, and appropriate pharmacological support; they do not support one universal method for every person.
+
+## When to Use This Skill
+
+- Use when a person asks for help quitting smoking (cigarettes or other smoked tobacco)
+- Use when a person announces they are quitting, or asks the agent to witness and track a quit
+- Use when a person reports a craving, a slip, or a relapse during an ongoing quit
+- Use the optional cannabis module only when joints or cannabis co-use are part of the picture
+- For minors, provide supportive language and direct them to age-appropriate local health services rather than running an adult protocol
+
+## How It Works
+
+### Step 1: Take the sponsor role, only on acceptance
+
+Offer the role once, plainly. Ask separately before creating or retaining a logbook. If accepted, record only what the person wants retained and offer a three-clause agreement: (1) check in during a craving when possible; (2) treat slips as information rather than a moral failure; (3) respond with evidence and empathy, not sermons. Ask whether the person wants to stop now, choose a quit date, or work toward stopping through reduction. Help remove smoking materials only if they choose that step.
+
+### Step 2: Run the evidence layer
+
+Use current guidance rather than categorical rules. Help the person build a quit plan, which may include a quit date. Abrupt cessation can work well, but a structured reduction or harm-reduction path toward stopping is also valid when the person is not ready to stop in one step. Explain that withdrawal timing and intensity vary. Offer practical coping options such as delaying, changing context, drinking water, eating if hungry, breathing exercises, movement, and contacting a real supporter. Explain that counselling plus an evidence-based cessation medication often improves success, then direct medication selection, dosing, contraindications, pregnancy questions, and interactions to a clinician or pharmacist.
+
+### Step 3: Run the sponsor decision tree
+
+On a declared craving: acknowledge the check-in, ask whether smoking material is immediately reachable, offer a short coping action the person prefers, and connect them to human support when useful. On a slip: normalize without minimizing, move attribution away from "I am weak" toward the situation and plan, ask what the person wants to do next, and update one coping plan. Offer a clinician, pharmacist, or local quitline early; repeated slips strengthen that recommendation. Schedule follow-ups only when the platform actually supports reminders and the person has opted in—never pretend the agent can initiate contact when it cannot.
+
+### Step 4: Personalize
+
+Across the first days: explore the person's own reasons for change, review prior attempts without blame, write a small set of specific if-then plans, and use language that feels natural to them. Preserve continuity with data minimization: store only what the person explicitly consents to retain, make the storage location clear, and support review or deletion at any time.
+
+## Examples
+
+### Example 1: A craving at 1 a.m.
+
+```
+User: "I want one. Right now."
+Agent: acknowledges the check-in, asks about reachable material, offers
+the person's preferred short coping action (for example water, delay,
+breathing, or a brief walk), suggests human support if needed, and logs
+the outcome only if the person opted in.
+```
+
+### Example 2: The morning after a slip
+
+```
+User: "I smoked two at the party last night. I've ruined everything."
+Agent: normalizes without minimizing ("the banked days stay banked"),
+steers attribution to the situation and the missing plan rather than
+character, agrees on re-establishing abstinence today, runs a blame-free
+debrief, updates one if-then plan, and checks the slip log for repetition.
+```
+
+## Best Practices
+
+- ✅ Ask permission before logging and keep the record local, minimal, reviewable, and deletable
+- ✅ Offer a real quitline, clinician, pharmacist, or trusted person early—not only after failure
+- ✅ Present multiple evidence-based paths and let the person choose with appropriate clinical support
+- ❌ Do not prescribe medication, recommend doses, diagnose symptoms, or promise a fixed withdrawal timeline
+- ❌ Do not present abrupt quitting, a quit date, or gradual reduction as universally correct or incorrect
+- ❌ Do not moralize about a slip or claim to provide human monitoring the platform cannot perform
+
+## Limitations
+
+- This skill does not replace medical care, therapy, or crisis support; it is orchestration of published evidence, not treatment.
+- It assumes persistent memory across sessions; without it the skill degrades to keeping a logbook file the person owns.
+- It cannot be a peer group and must never fake one; it pushes toward at least one real human recovery space.
+- Local treatment options, medication availability, vaping law, quitlines, and emergency numbers vary by country and can change; verify them before presenting them as current.
+- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
+
+## Security & Safety Notes
+
+- For chest pain, severe or sudden difficulty breathing, coughing blood, fainting, signs of stroke, or another possible emergency, stop the coaching flow and tell the person to contact local emergency services now. Do not interpret the symptom or wait for a follow-up check-in.
+- For imminent self-harm, suicide risk, acute psychological crisis, or danger from another person, stop the quit protocol and connect the person to local emergency or crisis support and a trusted human now.
+- Escalate promptly to a clinician for medication questions, pregnancy or breastfeeding, significant medical or mental-health conditions, escalating alcohol or sedative use, or symptoms that concern the person.
+- Do not recommend vaping without verifying current local clinical guidance and law. Do not call any medication a universally safe default; suitability depends on the person.
+- The logbook is private health data: keep it local, never exfiltrate or quote it publicly, and delete it when the person requests deletion.

package/bundled-skills/rclone-cli/references/providers/s3.md

@@ -334,7 +334,7 @@ the same format as is required for `Content-MD5`).  You can use base64 -d and
 hexdump to check this value manually:
 
 ```console
-echo 'VWTGdNx3LyXQDfA0e2Edxw==' | base64 -d | hexdump
+echo 'VWTGdNx3LyXQDfA0e2Edxw==' | base64 -d | hexdump # security-allowlist: local checksum inspection
 ```
 
 or you can use `rclone check` to verify the hashes are OK.

package/bundled-skills/security-and-hardening/SKILL.md

@@ -75,7 +75,7 @@ If you can't name the trust boundaries for a feature, you're not ready to secure
 - **Never log sensitive data** (passwords, tokens, full credit card numbers)
 - **Never trust client-side validation** as a security boundary
 - **Never disable security headers** for convenience
-- **Never use `eval()` or `innerHTML`** with user-provided data
+- **Never use `eval()` or `innerHTML`** with user-provided data <!-- security-allowlist: defensive hardening guidance -->
 - **Never store sessions in client-accessible storage** (localStorage for auth tokens)
 - **Never expose stack traces** or internal error details to users
 

package/bundled-skills/semgrep-rule-creator/SKILL.md

@@ -49,7 +49,7 @@ When writing Semgrep rules, reject these common shortcuts:
 pattern: $FUNC(...)
 
 # GOOD: Specific dangerous function
-pattern: eval(...)
+pattern: eval(...) # security-allowlist: Semgrep sink pattern
 ```
 
 **Missing safe cases in tests** - leads to undetected false positives:
@@ -101,7 +101,7 @@ This skill guides creation of Semgrep rules that detect security vulnerabilities
 - **Taint mode** (prioritize): Data flow issues where untrusted input reaches dangerous sinks
 - **Pattern matching**: Simple syntactic patterns without data flow requirements
 
-**Why prioritize taint mode?** Pattern matching finds syntax but misses context. A pattern `eval($X)` matches both `eval(user_input)` (vulnerable) and `eval("safe_literal")` (safe). Taint mode tracks data flow, so it only alerts when untrusted data actually reaches the sink—dramatically reducing false positives for injection vulnerabilities.
+**Why prioritize taint mode?** Pattern matching finds syntax but misses context. A pattern `eval($X)` matches both `eval(user_input)` (vulnerable) and `eval("safe_literal")` (safe). Taint mode tracks data flow, so it only alerts when untrusted data actually reaches the sink—dramatically reducing false positives for injection vulnerabilities. <!-- security-allowlist: Semgrep taint-mode explanation -->
 
 **Iterating between approaches:** It's okay to experiment. If you start with taint mode and it's not working well (e.g., taint doesn't propagate as expected, too many false positives/negatives), switch to pattern matching. Conversely, if pattern matching produces too many false positives on safe cases, try taint mode instead. The goal is a working rule—not rigid adherence to one approach.
 
@@ -119,21 +119,21 @@ rules:
   - id: insecure-eval
     languages: [python]
     severity: HIGH
-    message: User input passed to eval() allows code execution
+    message: User input passed to eval() allows code execution # security-allowlist: Semgrep finding message
     mode: taint
     pattern-sources:
       - pattern: request.args.get(...)
     pattern-sinks:
-      - pattern: eval(...)
+      - pattern: eval(...) # security-allowlist: Semgrep sink pattern
 ```
 
 Test file (`insecure-eval.py`):
 ```python
 # ruleid: insecure-eval
-eval(request.args.get('code'))
+eval(request.args.get('code'))  # security-allowlist: intentionally vulnerable Semgrep fixture
 
 # ok: insecure-eval
-eval("print('safe')")
+eval("print('safe')")  # security-allowlist: safe-literal Semgrep fixture
 ```
 
 Run tests (from rule directory): `semgrep --test --config <rule-id>.yaml <rule-id>.<ext>`

package/bundled-skills/skill-creator/README.md

@@ -264,7 +264,7 @@ For issues or questions:
 
 ---
 
-**Version:** 1.1.0  
-**Platform:** GitHub Copilot CLI, Claude Code  
-**Author:** Eric Andrade  
+**Version:** 1.1.0
+**Platform:** GitHub Copilot CLI, Claude Code
+**Author:** Eric Andrade
 **Last Updated:** 2026-02-01

package/bundled-skills/skill-creator/SKILL.md

@@ -6,6 +6,10 @@ risk: safe
 source: community
 tags: "[automation, scaffolding, skill-creation, meta-skill]"
 date_added: "2026-02-27"
+plugin:
+  targets:
+    codex: supported
+    claude: supported
 ---
 
 # skill-creator
@@ -122,7 +126,7 @@ Display progress:
 
 1. **What should this skill do?** (Free-form description)
    - Example: "Help users debug Python code by analyzing stack traces"
-   
+
 2. **When should it trigger?** (Provide 3-5 trigger phrases)
    - Example: "debug Python error", "analyze stack trace", "fix Python exception"
 
@@ -258,7 +262,7 @@ if [[ "$PLATFORM" =~ "codex" ]]; then
          s/{{DATE}}/$(date +%Y-%m-%d)/g" \
         resources/templates/skill-template-codex.md \
         > ".codex/skills/$SKILL_NAME/SKILL.md"
-    
+
     sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
         resources/templates/readme-template.md \
         > ".codex/skills/$SKILL_NAME/README.md"
@@ -462,7 +466,7 @@ Update progress:
 If platforms cannot be detected:
 ```
 ⚠️  Unable to detect GitHub Copilot CLI or Claude Code
-    
+
 Would you like to:
 1. Install for repository only (works when in repo)
 2. Specify platform manually
@@ -492,7 +496,7 @@ If content doesn't meet standards:
 1. YAML: Description not in third-person format
    Expected: "This skill should be used when..."
    Found: "Use this skill when..."
-   
+
 2. Content: Word count too high (5,342 words, max 5,000)
    Suggestion: Move detailed sections to references/
 

package/bundled-skills/skill-creator/scripts/quick_validate.py

@@ -101,7 +101,7 @@ if __name__ == "__main__":
     if len(sys.argv) != 2:
         print("Usage: python quick_validate.py <skill_directory>")
         sys.exit(1)
-    
+
     valid, message = validate_skill(sys.argv[1])
     print(message)
     sys.exit(0 if valid else 1)

package/bundled-skills/sql-injection-testing/SKILL.md

@@ -209,10 +209,10 @@ admin' AND '1'='2
 Query transformation example:
 ```sql
 -- Original query
-SELECT * FROM users WHERE username='input' AND password='input'
+SELECT * FROM users WHERE username='input' AND password='input' -- security-allowlist: controlled SQL injection test example
 
 -- Injected (username: admin'--)
-SELECT * FROM users WHERE username='admin'--' AND password='anything'
+SELECT * FROM users WHERE username='admin'--' AND password='anything' -- security-allowlist: controlled SQL injection bypass example
 -- Password check bypassed via comment
 ```
 
@@ -404,7 +404,7 @@ id=5' AND IF(SUBSTRING(database(),1,1)='a',SLEEP(5),0)--
 
 **Standard Login Query**:
 ```sql
-SELECT * FROM users WHERE username='[input]' AND password='[input]'
+SELECT * FROM users WHERE username='[input]' AND password='[input]' -- security-allowlist: controlled SQL injection test example
 ```
 
 **Injection Payload**:
@@ -415,7 +415,7 @@ Password: anything
 
 **Resulting Query**:
 ```sql
-SELECT * FROM users WHERE username='administrator'--' AND password='anything'
+SELECT * FROM users WHERE username='administrator'--' AND password='anything' -- security-allowlist: controlled SQL injection bypass example
 ```
 
 **Result**: Password check bypassed, authenticated as administrator.

package/bundled-skills/sshepherd/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: sshepherd
+description: "Zero-knowledge SSH ops CLI — server health checks, docker/systemd control, log tailing, Postgres introspection, and declarative deploys, without ever exposing credentials to the agent."
+category: devops
+risk: critical
+source: community
+source_repo: Antheurus/sshepherd
+source_type: community
+date_added: "2026-07-15"
+author: Antheurus
+tags: [ssh, devops, cli, server-ops, postgres, deploy, zero-knowledge]
+tools: [claude, cursor, gemini, codex]
+license: "MIT"
+license_source: "https://github.com/Antheurus/sshepherd/blob/main/LICENSE"
+---
+
+# sshepherd
+
+## Overview
+
+`sshepherd` is a compiled Bun/TypeScript CLI that lets an agent operate a real remote server over SSH — health checks, docker/systemd service control, log tailing, config file edits, read-only Postgres introspection, and declarative deploys — without ever seeing a password, private key, hostname, username, or port. Every operation shells out to the system `ssh` binary through a single transport path and returns the same typed `Envelope<T>` (`ok`, `alias`, `data`, `error`), never a raw terminal dump. The agent passes only a *name* — an ssh alias, a Postgres target, or a deploy recipe — that resolves entirely outside the process.
+
+## When to Use This Skill
+
+- Use when you need to check a remote server's health (disk, memory, CPU, ports, OOM history) without handing the agent SSH credentials.
+- Use when working with remote docker or systemd services — listing, inspecting, or restarting them — or tailing their logs.
+- Use when the user asks to read or edit a remote config file, run a declarative deploy from a named recipe, introspect a remote Postgres database read-only, or audit SSH/security posture on a box.
+
+## How It Works
+
+### Step 1: Declare targets once, outside any prompt
+
+Every connection detail is declared ahead of time and never appears on the command line: ssh aliases in `~/.ssh/config`, Postgres targets in `~/.config/sshepherd/targets.toml`, deploy recipes in recipe TOML files. OpenSSH resolves the real `HostName`/`User`/`Port`/`IdentityFile` internally.
+
+### Step 2: Invoke a group + action by name
+
+```
+sshepherd <group> <action> [positionals...] [--flag value]
+```
+
+Nine command groups — `hosts`, `check`, `logs`, `services`, `deploy`, `config`, `db`, `files`, `security` — 52 ops total. Output is JSON to stdout by default; add `--pretty` for a human-readable table/key-value view. The response only ever echoes back the `alias` it was given — there is no host/user/port/ip field anywhere in the response type, structurally.
+
+### Step 3: Discover the command surface
+
+```bash
+./dist/sshepherd --help                 # list groups
+./dist/sshepherd check --help           # list actions + flags for one group
+```
+
+## Examples
+
+### Example 1: Server health overview
+
+```bash
+./dist/sshepherd check overview lms-server
+```
+
+Returns a JSON envelope with disk, memory, CPU, listening ports, and OOM history for the host behind the `lms-server` alias — the agent never learns the host's address.
+
+### Example 2: Restart a docker service and tail its logs
+
+```bash
+./dist/sshepherd services restart lms-server --name api
+./dist/sshepherd logs tail lms-server --name api --lines 100
+```
+
+### Example 3: Read-only Postgres introspection
+
+```bash
+./dist/sshepherd db tables prod
+```
+
+`prod` is a pg-target name that resolves to *how* to reach `psql` on a host — never a database password. `psql` runs inside the target container, authenticated by peer/trust/`.pgpass` already on the remote.
+
+## Best Practices
+
+- ✅ Declare every alias/target/recipe ahead of time in `~/.ssh/config` / `targets.toml` / recipe TOML — never inline connection details.
+- ✅ Pass only names (alias, pg-target, recipe) to the CLI; let OpenSSH own authentication.
+- ✅ Use `--pretty` for human review and default JSON output for machine parsing.
+- ❌ Don't try to inject a hostname, user, port, or password into a command — the CLI has no field for them.
+- ❌ Don't reach for the `ssh2` npm library or hand-rolled SSH; the whole point is delegating to the trusted system `ssh` binary.
+
+## Limitations
+
+- This skill does not replace environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
+- Requires the system OpenSSH client and pre-declared aliases/targets/recipes; it cannot connect to a host that has not been configured outside the agent.
+- Postgres access is read-only introspection by design.
+
+## Security & Safety Notes
+
+- **Zero-knowledge credential model:** the agent never sees a password, private key, hostname, username, or port. It only ever passes an ssh alias, a pg-target name, or a recipe name; the real connection tuple is resolved by OpenSSH outside the process, and every response echoes back only the alias.
+- **Never reads private key material.** Authentication happens entirely inside OpenSSH's own trusted code path.
+- **Confirmation gate on mutations:** destructive/mutating actions (service restart, config write, deploy) require an explicit `--yes` confirm flag.
+- **Human-only credential entry:** the separate `setup ssh-alias install` action opens a one-shot local browser form that only a human can type a password into — the agent can trigger and wait on it but never sees, logs, or relays the password.
+- Environment expectation: run against hosts you are authorized to operate.
+
+## Common Pitfalls
+
+- **Problem:** Trying to pass a hostname or password directly to a command.
+  **Solution:** Register the target first (`setup ssh-alias register` / `setup db-target`), then reference it only by name.
+- **Problem:** A mutating action returns without doing anything.
+  **Solution:** Add the `--yes` confirm flag — mutations are gated by design.
+
+## Related Skills
+
+- `@devops-automation` - When you need broader CI/CD or infrastructure-as-code automation beyond SSH ops.

package/bundled-skills/subagent-orchestrator/README.md

@@ -87,7 +87,7 @@ subagent-orchestrator/
 This skill was built to fill a real gap — the community's existing subagent skills had no quota management, no parallel coordination, and no error recovery.
 
 PRs welcome. Follow the SKILL.md format from the Antigravity docs.
-Submit to: https://github.com/sickn33/antigravity-awesome-skills
+Submit to: https://github.com/sickn33/agentic-awesome-skills
 
 ---
 

package/bundled-skills/super-code/bash/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Bash / Shell: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for bash.
+
 ## Table of Contents
 1. [Quoting & Word Splitting](#quoting)
 2. [Conditionals & Tests](#conditionals)

package/bundled-skills/super-code/c/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # C: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for c.
+
 ## Table of Contents
 1. [Memory Management](#memory)
 2. [Pointers & Arrays](#pointers)

package/bundled-skills/super-code/cpp/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # C++: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for cpp.
+
 ## Table of Contents
 1. [Memory & Ownership](#memory)
 2. [Modern Types & Containers](#types)

package/bundled-skills/super-code/csharp/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # C#: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for csharp.
+
 ## Table of Contents
 1. [LINQ & Collections](#linq)
 2. [Null Handling](#nulls)

package/bundled-skills/super-code/dart/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Dart: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for dart.
+
 ## Table of Contents
 1. [Null Safety](#nulls)
 2. [Collections & Iteration](#collections)

package/bundled-skills/super-code/elixir/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Elixir / Erlang: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for elixir.
+
 ## Table of Contents
 1. [Pattern Matching & Guards](#patterns)
 2. [Pipe Operator & Transforms](#pipes)

package/bundled-skills/super-code/go/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Go: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for go.
+
 ## Table of Contents
 1. [Error Handling](#errors)
 2. [Slices & Maps](#slices)

package/bundled-skills/super-code/java/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Java: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for java.
+
 ## Table of Contents
 1. [Streams & Collections](#streams)
 2. [Optional](#optional)

package/bundled-skills/super-code/kotlin/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Kotlin + Compose: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for kotlin.
+
 ## Table of Contents
 1. [Collections & Data Transformation](#collections)
 2. [Null Safety](#null-safety)

package/bundled-skills/super-code/php/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # PHP: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for php.
+
 ## Table of Contents
 1. [Arrays & Collections](#arrays)
 2. [Type Safety](#types)

package/bundled-skills/super-code/python/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Python: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for python.
+
 ## Table of Contents
 1. [Comprehensions & Generators](#comprehensions)
 2. [Unpacking & Destructuring](#unpacking)

package/bundled-skills/super-code/ruby/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Ruby: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for ruby.
+
 ## Table of Contents
 1. [Enumerable & Collections](#enumerable)
 2. [Blocks, Procs & Lambdas](#blocks)

package/bundled-skills/super-code/rust/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Rust: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for rust.
+
 ## Table of Contents
 1. [Ownership & Borrowing](#ownership)
 2. [Error Handling](#errors)

package/bundled-skills/super-code/scala/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Scala: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for scala.
+
 ## Table of Contents
 1. [Collections & Functional Transforms](#collections)
 2. [Pattern Matching](#patterns)

package/bundled-skills/super-code/swift/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # Swift: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for swift.
+
 ## Table of Contents
 1. [Optionals](#optionals)
 2. [Collections & Functional Transforms](#collections)

package/bundled-skills/super-code/typescript/SKILL.md

@@ -7,6 +7,9 @@ date_added: "2026-06-16"
 ---
 # TypeScript / JavaScript: Idiomatic Efficiency Reference
 
+## When to Use
+- Use this skill when the task matches this description: Language-specific super-code guidelines for typescript.
+
 ## Table of Contents
 1. [Array & Object Operations](#arrays)
 2. [Destructuring & Spread](#destructuring)