Skills debugger
๐Ÿ“ฆ

debugger

Content revision r2 Medium Risk โš™๏ธ External commands

Debug Software with Structured Evidence

Intermittent bugs are difficult to isolate when evidence is incomplete. This skill structures hypotheses, captures diagnostic evidence, applies focused fixes, and verifies regressions.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 69 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "debugger" from https://skillstore.io/skills/cubha-debugger.md and its manifest at https://skillstore.io/api/skills/cubha-debugger/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "debugger". The checkout page fails after an expired session is refreshed.

Expected outcome:

Root cause: the refreshed session updates storage, but the checkout client retains the expired token. The fix refreshes client state before retrying.

Using "debugger". A profile form saves successfully but still displays the previous name.

Expected outcome:

  • Browser evidence shows a successful update response followed by a stale cached query.
  • The fix invalidates the profile query and the repeated scenario displays the new name.
  • Regression checks pass and temporary diagnostics are removed.

Security Audit

Medium Risk
v3 โ€ข 7/23/2026 Open versioned report

Two of 38 static findings are confirmed because the workflow runs project-controlled verification scripts that may execute arbitrary repository code. The remaining static findings are Markdown, safe examples, or explicit prohibitions. A separate medium-risk finding covers direct source edits and marker-based deletion.

1
Files scanned
225
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Direct Source Mutation and Marker-Based Deletion
The workflow inserts logs directly into source files, then removes each marker and its following line. A misplaced marker could delete unintended code.
The instructions explicitly require direct log insertion and pair-based deletion. The source mutation is intentional, while the unintended-deletion risk depends on marker integrity.
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
Ruby/shell backtick execution
4. **ํšŒ๊ท€ ๊ฒŒ์ดํŠธ** โ†’ ํ”„๋กœ์ ํŠธ ๊ฒ€์ฆ ์Šคํฌ๋ฆฝํŠธ(`verify.sh`, `npm test`, `npm run build`, `pytest` ๋“ฑ)๊ฐ€ ์žˆ์œผ๋ฉด ์‹คํ–‰. ์žฌํ˜„ ์ฆ์ƒ์€ ์‚ฌ
The workflow explicitly runs verify.sh, package scripts, builds, or tests. Repository-controlled scripts can execute arbitrary code without a stated confirmation step.
Medium
Ruby/shell backtick execution
3. **ํšŒ๊ท€ ๊ฒŒ์ดํŠธ** โ†’ ํ”„๋กœ์ ํŠธ ๊ฒ€์ฆ ์Šคํฌ๋ฆฝํŠธ(`verify.sh`, `npm test`, `npm run build`, `pytest` ๋“ฑ)๊ฐ€ ์žˆ์œผ๋ฉด ์‹คํ–‰. ์‹œ๋‚˜๋ฆฌ์˜ค ์žฌํ˜„์€
The Playwright workflow explicitly runs project verification scripts and package commands. Those repository-controlled commands can execute arbitrary code without a stated confirmation step.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/cubha-debugger/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/cubha-debugger/security.svg)](https://skillstore.io/skills/cubha-debugger?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/cubha-debugger?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cubha-debugger/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/cubha-debugger.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

cubha. (2026). debugger security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cubha-debugger/audits/3

BibTeX citation

@techreport{cubha-cubha-debugger-2026, author = {cubha}, title = {debugger security audit report (audit version 3)}, institution = {Skillstore}, year = {2026}, number = {3}, url = {https://skillstore.io/skills/cubha-debugger/audits/3}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "debugger security audit report (audit version 3)" version: "unspecified" type: report authors: - name: "cubha" date-released: "2026-07-23" url: "https://skillstore.io/skills/cubha-debugger/audits/3" identifiers: - type: other value: "skillstore:cubha-debugger:audit:3" description: "Skillstore immutable audit report identifier"

Compare variants

3 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
shubhamsaboo Recommended

shubhamsaboo-debugger

Skillstore Score 80
Evidence Confidence Medium
Skillstore usage 6
Updated

2026-08-21

sickn33-debugger

Skillstore Score 79
Evidence Confidence High
Skillstore usage 25
Updated

2026-08-21

cubha Current

cubha-debugger

Skillstore Score 69
Evidence Confidence Medium
Skillstore usage 4
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Trace an Application Error

Analyze a stack trace, add focused diagnostics, identify the failing path, and verify the fix.

Reproduce a Browser Defect

Use Playwright evidence to reproduce a web issue and compare behavior before and after a fix.

Repair a Cross-Module Regression

Check callers, data contracts, and shared state before applying a durable correction.

Try These Prompts

Diagnose an Error
Diagnose this error: [paste error]. Identify likely causes, inspect relevant files, and tell me what evidence you need before changing code.
Instrument an Intermittent Failure
Debug this intermittent failure in [feature]. Add temporary marked logs at the strongest hypotheses, then wait for my results before fixing anything.
Debug a Browser Scenario
Use --pw on [URL] to reproduce [scenario]. Capture console, network, screenshot, and DOM evidence, then fix and rerun the scenario.
Investigate a Boundary Regression
Investigate [bug] across [modules]. Check caller, API, data, and shared-state boundaries before applying a durable fix and running all available regression gates.

Best Practices

  • Provide the exact error, reproduction steps, environment, and recent changes.
  • Review proposed diagnostic locations before running the affected application.
  • Inspect every final diff and confirm that temporary logs were removed.

Avoid

  • Do not use this workflow for feature development or general code review.
  • Do not run project scripts from an untrusted repository without inspection and confirmation.
  • Do not include passwords, tokens, personal data, or production records in diagnostic output.

Frequently Asked Questions

Which languages support temporary logging?
The defined formats cover JavaScript, TypeScript, Python, Java, and Kotlin.
Does the skill require Playwright?
No. The default workflow uses user-provided logs. Playwright MCP is required only for --pw browser mode.
Will it change source files?
Yes. It can insert temporary logs, apply a focused fix, and remove its marked diagnostics.
How does it protect sensitive data?
The workflow requires masking passwords, tokens, and personal data. It also forbids logging in environment and secrets files.
How does it verify a fix?
It reruns the failing scenario and available project checks, such as tests, builds, linting, or type checks.
What happens when the cause remains unclear?
It adds limited diagnostic rounds, requests more reproduction details, and stops after the configured retry limit.

Developer Details

Author

cubha

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

c43861a65bb95efcae259cd161c9d6f4dc7eec6f

Maintenance freshness

7/24/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from cubha

View all
View all