[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERQMMESXB742C1RD1139DP":3,"skill-same:01M7ERQMMESXB742C1RD1139DP":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7ERQMMESXB742C1RD1139DP","security-check",null,"Use when auditing a Rails app for XSS, CSRF, SQLi, IDOR, secrets, or auth bypass. Never print secrets. Trigger words: security, audit, XSS, CSRF, SQL injection, vulnerability.","ga-arnez\u002Fhabii-base","ga-arnez","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171380296?v=4","01M7ERN055RRZGC541T4VJPWAP","01M7ERN05V02WTNTBGR3QYNYFK",0,"MIT","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-rails\u002Fskills\u002Fsecurity-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-check\ntype: atomic\nlicense: MIT\ndescription: >\n  Use when auditing a Rails app for XSS, CSRF, SQLi, IDOR, secrets, or auth\n  bypass. Never print secrets. Trigger words: security, audit, XSS, CSRF,\n  SQL injection, vulnerability.\nmetadata:\n  version: 1.0.0\n  user-invocable: \"true\"\n---\n\n# Security Check\n\n\n## HARD-GATE: Credential Handling\n\n```text\nCREDENTIAL HANDLING (W007 — Insecure Credential Exposure Defense):\n- NEVER reproduce credentials, tokens, API keys, passwords, or secrets verbatim\n  in output — flag by file path and line number only.\n- When a finding involves secrets in code or logs, report:\n    Affected file: app\u002Fconfig\u002Finitializers\u002Ffoo.rb:12\n    Finding: API key present in plain text — move to Rails credentials or ENV\n  Do NOT quote the secret value itself.\n- Exploitability Verification sub-sections MUST use generic placeholder values\n  (e.g. \"\u003CREDACTED>\", \"\u003CTOKEN>\") — never the actual credential.\n- If a file scan returns a secret value, stop — report its location, not its content.\n```\n\n## Quick Reference\n\n| Area | Key Checks |\n|------|------------|\n| Auth | Permissions on every sensitive action |\n| Params | No `permit!`, allowlist only safe attributes |\n| Queries | Parameterized — no string interpolation in SQL |\n| Redirects | Constrained to relative paths or allowlist |\n| Output | No `html_safe`\u002F`raw` on user content |\n| Secrets | Encrypted credentials, never in code or logs |\n| Files | Validate filename, content type, destination |\n\n## Core Process\n\n**Core principle:** Prioritize exploitable issues over style. Treat all untrusted input as potentially abused.\n\n### 0. Inspect the Workspace\nBefore writing any findings or analysis, you MUST run search and directory listing tools to find source files in the workspace (e.g. controllers, models, config files). Perform a code-level security review on the actual files found. Only if the workspace is completely empty may you return a checklist and state that no source files were provided.\n\n### Review Order\n\nReview in this sequence, and produce output sections in this same order:\n\n1. Authentication and authorization boundaries.\n2. Parameter handling and sensitive attribute assignment.\n3. Redirects, rendering, and output encoding.\n4. File handling, network calls, and background job inputs.\n5. Secrets, logging, and operational exposure.\n6. **Verify each finding:** Confirm it is exploitable with a concrete attack scenario before reporting. Exclude false positives (e.g., `html_safe` on a developer-defined constant, not user input).\n\n> **Validation gate:** The first output section must always be \"Authentication & Authorization\". If no auth\u002Fauthz issue exists, open with \"Authentication & Authorization: no issues found\" before any other category.\n\n### Severity Levels\n\n#### High\n\n- **Missing\u002Fbypassable authorization** — unprotected sensitive actions\n- **Injection** — SQL, shell, YAML, or constantization via user input\n- **Unsafe redirects \u002F SSRF** — outbound requests or redirects driven by user-controlled values\n- **Blind file upload trust** — filename, content type, or destination unvalidated\n- **Secrets in code\u002Flogs** — tokens or credentials committed or printed\n\n#### Medium\n\n- **Weak parameter filtering** — `permit!` or unscoped mass assignment\n- **Unsanitized HTML output** — user-controlled content rendered without sanitization\n- **Plaintext sensitive logging** — PII or credentials in log statements\n- **Hidden security behavior** — auth logic buried in callbacks or jobs without guardrails\n- **Brittle custom auth** — reimplements what framework primitives provide safely\n\n### Examples\n\n**High-severity (unscoped redirect):**\n\n```ruby\n# Bad: user-controlled redirect — open redirect \u002F phishing risk\nredirect_to params[:return_to]\n\n# Good: relative path only\nredirect_to root_path\n# Good: allowlist\nSAFE_PATHS = %w[\u002Fdashboard \u002Fsettings].freeze\nredirect_to(SAFE_PATHS.include?(params[:return_to]) ? params[:return_to] : root_path)\n```\n\n**Medium-severity (mass assignment):**\n\n```ruby\n# Bad: privilege escalation risk\nparams.require(:user).permit!\n\n# Good: explicit allowlist — never include role, admin, or privilege fields\nparams.require(:user).permit(:name, :email)\n```\n\n## Output Style\n\nWhen asked to perform a security audit, your output MUST include:\n\n1. **Section order** — One section per review area in the exact sequence specified; write \"No issues found\" for empty sections and note what evidence would be needed to verify that category\n2. **Finding details** — Each finding carries:\n   - **Severity:** **High** or **Medium** (not \"Critical\")\n   - **Attack path:** input → reach → impact\n   - **Affected file:** path + line, e.g. `app\u002Fcontrollers\u002Fdocuments_controller.rb:42`\n   - **Mitigation:** smallest credible fix\n   - **Hypothetical Exploitability Verification** sub-section: concrete example vulnerability and exploit request\u002Fpayload proving exploitability. This sub-section belongs inside Verification Steps & Quality Gates, never as a top-level section.\n3. **No Implied Paths** — When no source code is analyzed, use generic placeholders like `SRC_DIR\u002F` or `HYPOTHETICAL_DIR\u002Fhypothetical_controller.rb`\n4. **Language** — Must be in English unless explicitly requested otherwise\n\n## Extended Resources (Progressive Disclosure)\n\nLoad these files only when their specific content is needed:\n\n- **[PITFALLS.md](PITFALLS.md)** — Use when you need detailed examples of common security pitfalls and false positives to avoid\n\n## Integration\n\n| Skill | When to chain |\n|-------|---------------|\n| **code-review** | For full code review including non-security concerns |\n| **review-architecture** | When security issues stem from architectural problems |\n| **review-migration** | When reviewing migration security (data exposure, constraints) |\n| **security-review-process** *(from ruby-core-skills)* | Process discipline: OWASP checklist, Ruby-level security concerns |\n","# Security Check\n\n\n## HARD-GATE: Credential Handling\n\n```text\nCREDENTIAL HANDLING (W007 — Insecure Credential Exposure Defense):\n- NEVER reproduce credentials, tokens, API keys, passwords, or secrets verbatim\n  in output — flag by file path and line number only.\n- When a finding involves secrets in code or logs, report:\n    Affected file: app\u002Fconfig\u002Finitializers\u002Ffoo.rb:12\n    Finding: API key present in plain text — move to Rails credentials or ENV\n  Do NOT quote the secret value itself.\n- Exploitability Verification sub-sections MUST use generic placeholder values\n  (e.g. \"\u003CREDACTED>\", \"\u003CTOKEN>\") — never the actual credential.\n- If a file scan returns a secret value, stop — report its location, not its content.\n```\n\n## Quick Reference\n\n| Area | Key Checks |\n|------|------------|\n| Auth | Permissions on every sensitive action |\n| Params | No `permit!`, allowlist only safe attributes |\n| Queries | Parameterized — no string interpolation in SQL |\n| Redirects | Constrained to relative paths or allowlist |\n| Output | No `html_safe`\u002F`raw` on user content |\n| Secrets | Encrypted credentials, never in code or logs |\n| Files | Validate filename, content type, destination |\n\n## Core Process\n\n**Core principle:** Prioritize exploitable issues over style. Treat all untrusted input as potentially abused.\n\n### 0. Inspect the Workspace\nBefore writing any findings or analysis, you MUST run search and directory listing tools to find source files in the workspace (e.g. controllers, models, config files). Perform a code-level security review on the actual files found. Only if the workspace is completely empty may you return a checklist and state that no source files were provided.\n\n### Review Order\n\nReview in this sequence, and produce output sections in this same order:\n\n1. Authentication and authorization boundaries.\n2. Parameter handling and sensitive attribute assignment.\n3. Redirects, rendering, and output encoding.\n4. File handling, network calls, and background job inputs.\n5. Secrets, logging, and operational exposure.\n6. **Verify each finding:** Confirm it is exploitable with a concrete attack scenario before reporting. Exclude false positives (e.g., `html_safe` on a developer-defined constant, not user input).\n\n> **Validation gate:** The first output section must always be \"Authentication & Authorization\". If no auth\u002Fauthz issue exists, open with \"Authentication & Authorization: no issues found\" before any other category.\n\n### Severity Levels\n\n#### High\n\n- **Missing\u002Fbypassable authorization** — unprotected sensitive actions\n- **Injection** — SQL, shell, YAML, or constantization via user input\n- **Unsafe redirects \u002F SSRF** — outbound requests or redirects driven by user-controlled values\n- **Blind file upload trust** — filename, content type, or destination unvalidated\n- **Secrets in code\u002Flogs** — tokens or credentials committed or printed\n\n#### Medium\n\n- **Weak parameter filtering** — `permit!` or unscoped mass assignment\n- **Unsanitized HTML output** — user-controlled content rendered without sanitization\n- **Plaintext sensitive logging** — PII or credentials in log statements\n- **Hidden security behavior** — auth logic buried in callbacks or jobs without guardrails\n- **Brittle custom auth** — reimplements what framework primitives provide safely\n\n### Examples\n\n**High-severity (unscoped redirect):**\n\n```ruby\n# Bad: user-controlled redirect — open redirect \u002F phishing risk\nredirect_to params[:return_to]\n\n# Good: relative path only\nredirect_to root_path\n# Good: allowlist\nSAFE_PATHS = %w[\u002Fdashboard \u002Fsettings].freeze\nredirect_to(SAFE_PATHS.include?(params[:return_to]) ? params[:return_to] : root_path)\n```\n\n**Medium-severity (mass assignment):**\n\n```ruby\n# Bad: privilege escalation risk\nparams.require(:user).permit!\n\n# Good: explicit allowlist — never include role, admin, or privilege fields\nparams.require(:user).permit(:name, :email)\n```\n\n## Output Style\n\nWhen asked to perform a security audit, your output MUST include:\n\n1. **Section order** — One section per review area in the exact sequence specified; write \"No issues found\" for empty sections and note what evidence would be needed to verify that category\n2. **Finding details** — Each finding carries:\n   - **Severity:** **High** or **Medium** (not \"Critical\")\n   - **Attack path:** input → reach → impact\n   - **Affected file:** path + line, e.g. `app\u002Fcontrollers\u002Fdocuments_controller.rb:42`\n   - **Mitigation:** smallest credible fix\n   - **Hypothetical Exploitability Verification** sub-section: concrete example vulnerability and exploit request\u002Fpayload proving exploitability. This sub-section belongs inside Verification Steps & Quality Gates, never as a top-level section.\n3. **No Implied Paths** — When no source code is analyzed, use generic placeholders like `SRC_DIR\u002F` or `HYPOTHETICAL_DIR\u002Fhypothetical_controller.rb`\n4. **Language** — Must be in English unless explicitly requested otherwise\n\n## Extended Resources (Progressive Disclosure)\n\nLoad these files only when their specific content is needed:\n\n- **[PITFALLS.md](PITFALLS.md)** — Use when you need detailed examples of common security pitfalls and false positives to avoid\n\n## Integration\n\n| Skill | When to chain |\n|-------|---------------|\n| **code-review** | For full code review including non-security concerns |\n| **review-architecture** | When security issues stem from architectural problems |\n| **review-migration** | When reviewing migration security (data exposure, constraints) |\n| **security-review-process** *(from ruby-core-skills)* | Process discipline: OWASP checklist, Ruby-level security concerns |\n",{"name":5,"type":23,"license":14,"metadata":24,"description":27},"atomic",{"version":25,"user-invocable":26},"1.0.0","true","Use when auditing a Rails app for XSS, CSRF, SQLi, IDOR, secrets, or auth bypass. Never print secrets. Trigger words: security, audit, XSS, CSRF, SQL injection, vulnerability.\n","main","673b9947a5ae59be5e46a590b2dddb529b8461ba","plugins\u002Fhabii-rails\u002Fskills\u002Fsecurity-check","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base","https:\u002F\u002Fgithub.com\u002Fga-arnez","2026-11-13 05:04:20",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ga-arnez\u002Fhabii-base --skill security-check",{"tool":40,"command":41},"bunx","bunx skills add ga-arnez\u002Fhabii-base --skill security-check",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ga-arnez\u002Fhabii-base --skill security-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-rails\u002Fskills\u002Fsecurity-check\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"PITFALLS.md","REFERENCE","参考文档",818,"https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-rails\u002Fskills\u002Fsecurity-check\u002FPITFALLS.md",[55,62,69,76,83,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7ERS7Y51EDYAWW4NVTXH722","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7ERS2YQMAPNHTXQ011SZEPF","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7ERREG7BR55CZYE944RKBK3","prisma-client-api","Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on \"prisma query\", \"findMany\", \"create\", \"update\", \"delete\", \"$transaction\".","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fprisma-client-api\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7ERRAMGZJ0W08Y98D6ZC6WV","prisma-cli","Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fprisma-cli\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7ERR7K7RJR1CW1SB7RW769B","frontend-design","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7ERQH0PZQP73WC380M5M1NJ","optimize-performance","Use when investigating N+1s, slow queries, caching, or query plans in Rails. Profile before changing code. Trigger words: N+1, slow, performance, caching, EXPLAIN.","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-rails\u002Fskills\u002Foptimize-performance\u002FSKILL.md",[],[]]