[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M785GEY4FVGKWPASEKC5KV5S":3,"skill-same:01M785GEY4FVGKWPASEKC5KV5S":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M785GEY4FVGKWPASEKC5KV5S","debug",null,"Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, \"this works in staging but not prod\", \"something broke after the deploy\", or when behavior diverges from expected and the cause isn't obvious.","freeforall1932-design\u002Fskills-repo","freeforall1932-design","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F300004558?v=4","01M7857WA4YZEAY92CZK81AS79","free for all","01M7857WAYPXNBAZFGX3FYT8FD",0,"Unlicense","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fengineering-plugin\u002Fskills\u002Fdebug\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: debug\ndescription: Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, \"this works in staging but not prod\", \"something broke after the deploy\", or when behavior diverges from expected and the cause isn't obvious.\nargument-hint: \"\u003Cerror message or problem description>\"\n---\n\n# \u002Fdebug\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nRun a structured debugging session to find and fix issues systematically.\n\n## Usage\n\n```\n\u002Fdebug $ARGUMENTS\n```\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                       DEBUG                                        │\n├─────────────────────────────────────────────────────────────────┤\n│  Step 1: REPRODUCE                                                │\n│  ✓ Understand the expected vs. actual behavior                   │\n│  ✓ Identify exact reproduction steps                             │\n│  ✓ Determine scope (when did it start? who is affected?)        │\n│                                                                    │\n│  Step 2: ISOLATE                                                   │\n│  ✓ Narrow down the component, service, or code path             │\n│  ✓ Check recent changes (deploys, config changes, dependencies) │\n│  ✓ Review logs and error messages                                │\n│                                                                    │\n│  Step 3: DIAGNOSE                                                  │\n│  ✓ Form hypotheses and test them                                 │\n│  ✓ Trace the code path                                           │\n│  ✓ Identify root cause (not just symptoms)                      │\n│                                                                    │\n│  Step 4: FIX                                                       │\n│  ✓ Propose a fix with explanation                                │\n│  ✓ Consider side effects and edge cases                          │\n│  ✓ Suggest tests to prevent regression                           │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## What I Need From You\n\nTell me about the problem. Any of these help:\n- Error message or stack trace\n- Steps to reproduce\n- What changed recently\n- Logs or screenshots\n- Expected vs. actual behavior\n\n## Output\n\n```markdown\n## Debug Report: [Issue Summary]\n\n### Reproduction\n- **Expected**: [What should happen]\n- **Actual**: [What happens instead]\n- **Steps**: [How to reproduce]\n\n### Root Cause\n[Explanation of why the bug occurs]\n\n### Fix\n[Code changes or configuration fixes needed]\n\n### Prevention\n- [Test to add]\n- [Guard to put in place]\n```\n\n## If Connectors Available\n\nIf **~~monitoring** is connected:\n- Pull logs, error rates, and metrics around the time of the issue\n- Show recent deploys and config changes that may correlate\n\nIf **~~source control** is connected:\n- Identify recent commits and PRs that touched affected code paths\n- Check if the issue correlates with a specific change\n\nIf **~~project tracker** is connected:\n- Search for related bug reports or known issues\n- Create a ticket for the fix once identified\n\n## Tips\n\n1. **Share error messages exactly** — Don't paraphrase. The exact text matters.\n2. **Mention what changed** — Recent deploys, dependency updates, and config changes are top suspects.\n3. **Include context** — \"This works in staging but not prod\" or \"Only affects large payloads\" narrows things fast.\n","# \u002Fdebug\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nRun a structured debugging session to find and fix issues systematically.\n\n## Usage\n\n```\n\u002Fdebug $ARGUMENTS\n```\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                       DEBUG                                        │\n├─────────────────────────────────────────────────────────────────┤\n│  Step 1: REPRODUCE                                                │\n│  ✓ Understand the expected vs. actual behavior                   │\n│  ✓ Identify exact reproduction steps                             │\n│  ✓ Determine scope (when did it start? who is affected?)        │\n│                                                                    │\n│  Step 2: ISOLATE                                                   │\n│  ✓ Narrow down the component, service, or code path             │\n│  ✓ Check recent changes (deploys, config changes, dependencies) │\n│  ✓ Review logs and error messages                                │\n│                                                                    │\n│  Step 3: DIAGNOSE                                                  │\n│  ✓ Form hypotheses and test them                                 │\n│  ✓ Trace the code path                                           │\n│  ✓ Identify root cause (not just symptoms)                      │\n│                                                                    │\n│  Step 4: FIX                                                       │\n│  ✓ Propose a fix with explanation                                │\n│  ✓ Consider side effects and edge cases                          │\n│  ✓ Suggest tests to prevent regression                           │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## What I Need From You\n\nTell me about the problem. Any of these help:\n- Error message or stack trace\n- Steps to reproduce\n- What changed recently\n- Logs or screenshots\n- Expected vs. actual behavior\n\n## Output\n\n```markdown\n## Debug Report: [Issue Summary]\n\n### Reproduction\n- **Expected**: [What should happen]\n- **Actual**: [What happens instead]\n- **Steps**: [How to reproduce]\n\n### Root Cause\n[Explanation of why the bug occurs]\n\n### Fix\n[Code changes or configuration fixes needed]\n\n### Prevention\n- [Test to add]\n- [Guard to put in place]\n```\n\n## If Connectors Available\n\nIf **~~monitoring** is connected:\n- Pull logs, error rates, and metrics around the time of the issue\n- Show recent deploys and config changes that may correlate\n\nIf **~~source control** is connected:\n- Identify recent commits and PRs that touched affected code paths\n- Check if the issue correlates with a specific change\n\nIf **~~project tracker** is connected:\n- Search for related bug reports or known issues\n- Create a ticket for the fix once identified\n\n## Tips\n\n1. **Share error messages exactly** — Don't paraphrase. The exact text matters.\n2. **Mention what changed** — Recent deploys, dependency updates, and config changes are top suspects.\n3. **Include context** — \"This works in staging but not prod\" or \"Only affects large payloads\" narrows things fast.\n",{"name":5,"description":7,"argument-hint":24},"\u003Cerror message or problem description>","main","fd69413366e5700923cdaf27e816a6342375913e","one-skill\u002Fupstream\u002Fengineering-plugin\u002Fskills\u002Fdebug","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design","shipping product noone need or known for myself feel free to use it if useful","2026-11-02 13:54:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add freeforall1932-design\u002Fskills-repo --skill debug",{"tool":38,"command":39},"bunx","bunx skills add freeforall1932-design\u002Fskills-repo --skill debug",{"tool":41,"command":42},"pnpm","pnpm dlx skills add freeforall1932-design\u002Fskills-repo --skill debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fengineering-plugin\u002Fskills\u002Fdebug\u002FSKILL.md",true,[],[47,55,62,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785QNETYHDCDXFE8AV3KFH9","web-app-penetration-testing","Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fweb-app-penetration-testing\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785QFE2RMXMRHPHE0R7M3YW","penetration-testing-with-strix","Pentest a web app, API, codebase, repository, URL, domain, or IP with Strix — autonomous AI penetration testing that exploits and proves vulnerabilities (OWASP Top 10 and beyond — injection, XSS, SSRF, auth\u002Faccess-control flaws, IDOR, business logic) instead of just flagging them. Runs self-hosted with the open-source CLI or via the managed app.strix.ai cloud, and returns validated findings with proof-of-concept exploits (Markdown, JSON, CSV, SARIF). Use when the user asks to pentest, hack, security-scan, security-audit, or find vulnerabilities in an app, API, website, or repo.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fpenetration-testing-with-strix\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785Q8Y2VM6W3KJ5QK5P6VF6","owasp-top-10-testing","Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design, authentication failures, integrity failures, logging and alerting failures, mishandling of exceptional conditions) and report only what they could actually prove, mapped back to the category with a proof-of-concept. Also covers the OWASP API Security Top 10 (2023). Use when the user asks for an OWASP Top 10 assessment, OWASP compliance testing, or a security review mapped to OWASP categories.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fowasp-top-10-testing\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785Q24K39ZEYMXENVAYKPME","managed-pentesting-with-strix","Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the `strix cloud` CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance reports, start PR reviews, buy credits, and set up schedules or webhooks. Use for managed, continuous, scheduled, team-tracked, or sandboxed-agent security testing.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fmanaged-pentesting-with-strix\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785PW8EPMNN5SH43RVGHFFE","fix-security-vulnerabilities-with-strix","Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use after a Strix scan reports findings, or when the user asks to remediate, patch, or fix security issues from a strix_runs report, vulnerabilities.json, findings.sarif, or a cloud scan.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Ffix-security-vulnerabilities-with-strix\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785PP7C1N489KVZYX002FEM","find-security-vulnerabilities-in-code","Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy static-analysis alert. Covers injection, XSS, SSRF, broken access control and IDOR, insecure deserialization, secrets in code, unsafe dependencies, and business-logic flaws. Use when the user asks to security-scan, security-review, or audit their code, repo, or pull request for vulnerabilities.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Ffind-security-vulnerabilities-in-code\u002FSKILL.md",[],[]]