stack-trace-python-probe
Internal helper for meta-stack-trace-investigator. Use when a Python traceback needs Python-specific root-cause checks, pytest reproducer guidance, and defensive patch targets.
Profile →npx skills add opensquilla/opensquilla --skill stack-trace-python-probe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Stack Trace Python Probe Return only: ``` LANGUAGE_PROBE: python CHECKS: - <exception contract or missing-key/None-handling check> - <import/module/package boundary check if relevant> REPRODUCER: - <minimal pytest or python -c reproduction command/snippet> PATCH_TARGETS: - <guard clause / TypedDict / pydantic/schema validation / exception wrapping target> VERIFY: - <targeted pytest command or python syntax/import check> ``` Prefer `pytest -k <symbol>` and `python -m pytest <path>` shapes. Do not recommend destructive commands.
What does the stack-trace-python-probe skill do?
Internal helper for meta-stack-trace-investigator. Use when a Python traceback needs Python-specific root-cause checks, pytest reproducer guidance, and defensive patch targets.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill stack-trace-python-probe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.