gauntlet-curate
Audits the DSA problem bank for coverage gaps and proposes new YAML entries. Use when refreshing the problem bank during update-plugins runs.
What this skill does
# Gauntlet Curate
Survey the DSA problem bank, identify coverage gaps, and propose
new YAML entries for human review.
## When This Skill Fires
Invoke this skill manually with `Skill(gauntlet:gauntlet-curate)`
when the problem bank needs a coverage review. The skill is intended
to participate in `/update-plugins` runs but is not yet wired into
that command (see openpackage.yml registration). It is distinct from
`gauntlet:curate`, which handles per-annotation knowledge capture
and is what `/gauntlet-curate` invokes today.
## Steps
1. **Locate the problem bank** at `plugins/gauntlet/data/problems/`.
Read `_manifest.yaml` to load the expected NeetCode counts per
category.
2. **Survey current coverage** by counting problems in each YAML
file (skipping `_manifest.yaml`).
Run the analysis script:
```bash
cd plugins/gauntlet
python scripts/curate_problems.py data/problems/ --output /tmp/gauntlet-curate-report.md
```
3. **Identify gaps**: categories whose actual count falls below
the `neetcode_count` in the manifest.
The script sorts gaps largest-first so the worst shortfalls
appear at the top.
4. **Review existing problems** in each gap category to understand
what is already covered before proposing additions.
5. **Propose new YAML entries** following the schema below.
Add proposals to the report under "Proposed New Problems".
Do NOT write proposals directly into `data/problems/*.yaml`.
6. **Validate proposals** by running:
```bash
python -c "
import yaml, sys
sys.path.insert(0, 'src')
from gauntlet.models import BankProblem
proposals = yaml.safe_load(open('proposals.yaml'))
for p in proposals:
BankProblem.from_dict(p)
print('All proposals valid.')
"
```
7. **Present the report** to the human for review.
The report includes the coverage table, gap list, and proposed
entries.
The human decides which proposals to merge into the YAML files.
## Problem Schema
Each proposed entry must follow this schema:
```yaml
- id: category-NNN
title: Problem Title
difficulty: easy # easy | medium | hard | extra_hard
prompt: |
Problem statement with constraints and examples.
hints:
- First hint.
- Second hint.
solution_outline: |
Approach and time/space complexity.
tags: [tag1, tag2]
neetcode_id: neetcode-NNN
challenge_type: explain_why # explain_why | multiple_choice | trace
# | code_complete | debug | rank
```
Required fields: `id`, `title`, `difficulty`, `prompt`.
Optional fields default to empty values.
## Safety Constraints
- Never modify files under `data/problems/` directly.
- Never run with a `--write` or `--fix` flag: the script
intentionally has none.
- All output is a proposal report for human approval.
- Existing hand-curated problems are never touched.
## Output
A markdown report at the path specified by `--output`, containing:
- Coverage summary table (expected vs. actual per category)
- Gaps list sorted by missing count
- YAML schema template for new proposals
- Space for the human reviewer to add proposed entries
Human review is required before any YAML file changes.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.