テスト設計、脆弱性診断、品質保証（1.3万 件）
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
日本語の概要は準備中です。原文の説明を表示しています。
X (Twitter) integration for NanoClaw. Post tweets, like, reply, retweet, and quote. Use for setup, testing, or troubleshooting X functionality. Triggers on "setup x", "x integration", "twitter", "post tweet", "tweet".
日本語の概要は準備中です。原文の説明を表示しています。
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a composer output against four hard checks before delivery — cite integrity, voice rules, word count, schema validity. Always invoked after the polisher (English) or humanizer-* (Arabic / Hebrew). Emits a VerificationReport Pydantic object; orchestrator branches on `overall_passed`. Target ≥0.9 score per run. Triggers automatically as the final composer sub-agent; not user-facing.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive documentation audit and refresh. Checks code-documentation drift, generates prioritized report, then updates with approval. Use for: 'ドキュメント監査', 'docs audit', 'ドキュメント棚卸し', 'README全体見直し', 'documentation health check'.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze PermissionRequest decision logs and improve auto-approve configuration across all layers. Covers settings.json patterns, static rule engine, LLM evaluator prompt, and tests. Use when asked to "update auto-approve", "improve permissions", "reduce unnecessary asks", or "optimize permission rules".
日本語の概要は準備中です。原文の説明を表示しています。
Validate logical consistency of decisions and claims through context forking. Use proactively when judgment validity is unclear, but prefer direct tools (Read, Bash) for simple verifications like file contents or test results.
日本語の概要は準備中です。原文の説明を表示しています。
Standardized bug fix workflow using TDD (Red-Green-Refactor). Use when fixing bugs, resolving issues, or when the user invokes /bugfix. Ensures root cause analysis, failing test first, then minimal fix.
日本語の概要は準備中です。原文の説明を表示しています。
Policy-enforcing installer that deploys hardened Claude Code Action workflows (`@claude` manual mention + dependency-bot auto-fix) into a personal GitHub repository the user administers. Use when asked to introduce Claude Code Action, apply `@claude` mention support, or set up automated CI auto-fix for dependency bot PRs, using the security-hardened templates shipped with this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Design test viewpoints and test cases from code changes using ISO 25010. Use when writing test plans for plan.md, reviewing PR test coverage, or when asked to 'テスト設計', 'テスト観点洗い出し', 'design test cases'. Do NOT use for writing test code or TDD workflows (use /bugfix).
日本語の概要は準備中です。原文の説明を表示しています。
Execute a pre-existing plan file by implementing tasks sequentially with test verification after each step. Use when plan/tasks are already decomposed and ready for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when exiting plan mode or before implementing to verify ADR intent, OBPI scope and plan agree.
日本語の概要は準備中です。原文の説明を表示しています。
Namespace router → context preservation and orientation skills, plus the focused-context loader `gz context <ADR-ID>`. Use to pick the context/handoff intent or to load one ADR's full context bundle (body + OBPI briefs + covering tests + governance rules) before invoking the matched concrete skill or piping payload to an agent harness.
日本語の概要は準備中です。原文の説明を表示しています。
Use to wrap QA commands in ARB receipts for attestation evidence or to audit lint patterns from receipts.
日本語の概要は準備中です。原文の説明を表示しています。
Namespace router → the four-axis health and integrity audit, read through four dimensions of agent movement (change point, jurisdiction, invariant, escalation). Use when the operator reports that gzkit feels "wobbly", misaligned, or that governance is not holding — or before a release, to check that declared mechanisms still fire. Routes to the concrete axis surfaces in a fixed cheapest-first order; owns the ordering rationale, the reading frame and the budget rule, not the analyses themselves.
日本語の概要は準備中です。原文の説明を表示しています。
Use to verify every CLI command has its manpage, headings and index entry.
日本語の概要は準備中です。原文の説明を表示しています。
Use for an ADR's Gate-5 audit; provides the audit templates and procedure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the operator says "fly sortie S<N>" or "run a flight test"; flies one sortie with a human Go/No-Go.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a dev build of Spare (macOS menu bar app + `spare` CLI) the way a user does and capture proof. Use before claiming a Spare change works, to reproduce a bug, or when asked to verify/test Spare end to end.
日本語の概要は準備中です。原文の説明を表示しています。
Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, components, and AI-generated code. Use when reviewing code that touches user data, PII, or access control, or before any deploy of an app with auth.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and optimize an existing Convex app: security, scale, upgrades, observability.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.
日本語の概要は準備中です。原文の説明を表示しています。
Convex code reviewer — security, auth, validators, performance, and pattern checks for code in a convex/ directory. Use to review or audit Convex functions before shipping.
日本語の概要は準備中です。原文の説明を表示しています。