stack-trace-js-probe
stack-trace-js-probe is an internal diagnostic helper that analyzes JavaScript and TypeScript stack traces to identify root causes by checking async boundaries, property access errors, module resolution issues, and type contract violations. Use it when debugging Node.js, npm, or TypeScript compilation failures to generate targeted reproduction commands, pinpoint patch locations like optional chaining or validation gaps, and suggest verification test commands.
git clone --depth 1 https://github.com/opensquilla/opensquilla /tmp/stack-trace-js-probe && cp -r /tmp/stack-trace-js-probe/src/opensquilla/skills/bundled/stack-trace-js-probe ~/.claude/skills/stack-trace-js-probeSKILL.md
# Stack Trace JS Probe Return only: ``` LANGUAGE_PROBE: javascript-typescript CHECKS: - <async boundary / undefined property / JSON parsing / module-resolution check> - <TypeScript type-contract check if .ts/.tsx appears> REPRODUCER: - <minimal node/npm/vitest/jest/ts-node reproduction command or snippet> PATCH_TARGETS: - <optional chaining / schema validation / discriminated union / error wrapping target> VERIFY: - <npm test/vitest/jest/tsc command> ``` Pick JavaScript or TypeScript commands from the trace context. If the context does not identify a package manager, use generic `npm test -- <pattern>` or `npx tsc --noEmit` as examples.
Submit audio or video for multilingual dubbing, poll status, and download dubbed audio. Use when the user asks for dubbing, 多语言配音, 视频翻译配音, 译制片, or wants a source clip dubbed into another language.
Generate a structured short-video shooting script from a topic. Emits a strict, machine-parseable shot list (3 shots by default) with image prompt + video prompt + voiceover + on-screen text per shot. Trigger when the user asks for a video script, 分镜, 短视频文案, AI视频, 短剧脚本, or wants visual prompts ready for image/video generation.
Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.
Multi-round research with explicit methodology, evidence tracking, and citation-tagged synthesis. Trigger on 'deep dive', 'research report', 'literature review', 'investigate X across sources', 'multi-round investigation'. Distinct from the `summarize` skill, which is a single-pass condensation; this skill maintains a state file across iterations, tracks coverage, and produces a long-form report with per-claim citations. Three execution stages: plan (scope into sub-questions), iterate (record evidence per round), compile (synthesize report). The skill itself does not fetch the web — it tells the host agent which fetches to perform via OpenSquilla's existing web tools, and records what comes back.
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
Capture the current git diff (staged, working-tree, or staged file list) as text. Direct shell call for workflows that need repository diffs without an LLM agent loop.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'