1.3万 件 ・ 関連度順
Use before non-trivial coding work to pick a task-appropriate working mode — debug, fix, review, test-first, refactor, optimize, migrate, upgrade, integrate, spike, or unstuck — then follow its checklist. Modes are procedures, not personas. Not needed for trivial one-line edits or non-coding tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Fallback for general coding work that does not match any specific sextant sub-skill. Use for lightweight tasks: config changes, style fixes, utility functions, one-off scripts, or tasks too small to warrant a dedicated workflow. All dedicated sub-skills take priority over this one — check these first: sextant:fix-bug (broken behavior), sextant:debug (unknown bug location), sextant:add-feature (new functionality), sextant:modify-feature (changing existing behavior), sextant:review-code (evaluating code), sextant:write-tests (test coverage), sextant:refine-requirements (ambiguous scope), sextant:plan (multi-step sequencing), sextant:ship (release prep), sextant:migrate (cross-module upgrade), sextant:security (vulnerability audit). Only use this skill when none of the above match.
日本語の概要は準備中です。原文の説明を表示しています。
proposal.md が /spec の入力として十分な情報を含んでいるかを確認する。「ユーザーにとっての承認」ではなく「/spec にとっての準備完了度」を検証する軽量チェック
Verify data validity through Openapi Trust - email deliverability, mobile number HLR checks, IP reputation, URL safety scans, document-based identity verification (IDV). Use for anti-fraud validation of user-provided contact data and identities.
日本語の概要は準備中です。原文の説明を表示しています。
Authenticate with the Openapi marketplace (oauth.openapi.com). Use when you need to create, inspect, renew or delete Bearer tokens, list available scopes, check wallet credit, subscriptions, or API usage stats. Required by every other openapi-* skill.
日本語の概要は準備中です。原文の説明を表示しています。
Vehicle data through Openapi Automotive - look up cars, motorcycles, insurance and MOT status by license plate across Italy, UK, Germany, France, Spain, Portugal. Use for vehicle technical data and insurance validity checks by plate.
日本語の概要は準備中です。原文の説明を表示しています。
Write the spec before the code, then check the built thing against it — so agents build what was agreed, not what they invented.
日本語の概要は準備中です。原文の説明を表示しています。
Design better agents, skills and hooks for Claude Code, checking the current spec instead of guessing at fields.
日本語の概要は準備中です。原文の説明を表示しています。
Run the project's own tests, linter, type checker and build, and report what actually failed.
日本語の概要は準備中です。原文の説明を表示しています。
Bridge Codex to web-based AI model products by packaging local task context, scrub-checking it, sending it through an approved browser surface to ChatGPT Pro, Claude, Grok, Gemini, or another web model, waiting for the answer, and returning the model response to the user or Codex. Also guide DevSpace-like MCP Connector Mode when the user wants ChatGPT Pro or another MCP-capable web host to access approved local workspaces without relying on Codex browser automation. Use when the user asks for GPT Pro, ChatGPT Pro, Claude web, Grok, Gemini web, web model bridge, external model consult, ask another model, second opinion, use a web AI model, browserless agent access to GPT Pro, MCP connector, DevSpace-like workflow, or send local repo context to a browser-based model for planning, review, debugging, architecture discussion, or implementation guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Audits UI layout, overflow and navigation across product-defined viewports using consumer context and browser tools. Use when asked to check responsiveness, test mobile layout or audit breakpoint behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Configures shared sources and drafts context with independent writers. Plain/fresh setup offers installation of user-named packages and reuses built-in browser capabilities, adding browser tooling only for an evidenced required-check gap. Use for setup, source repair, writing context or refreshing drafts. Configure-only skips tooling and authoring; installations and activation require separate approval.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews existing UI components for design-system consistency, states, responsiveness and accessibility using consumer-owned context. Use when asked to review component quality, check design-system adherence or audit component consistency.
日本語の概要は準備中です。原文の説明を表示しています。
Passive code-review lane for authorized repositories, local checkouts, uploaded source archives, and diffs. Use when the security research agent needs deterministic candidate discovery before expensive AI investigation, scoped PR-style review, append-only evidence records, or independent revalidation of code findings.
日本語の概要は準備中です。原文の説明を表示しています。
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
日本語の概要は準備中です。原文の説明を表示しています。
Plan and run safe reverse engineering, decompilation, disassembly, instrumentation, de-obfuscation, and anti-analysis countermeasures for binaries, firmware, mobile apps, WebAssembly, JavaScript bundles, and .NET assemblies. Use for behavior reconstruction, cross-layer Electron tracing, REA, reversing strategy, decompiler selection, binary analysis, malware-style triage, unpacking, deobfuscation, defeating anti-debug or anti-VM checks, Wakaru, Ghidra, IDA, RetDec, radare2, Rizin, Frida, angr, YARA, or command scripts that capture analysis stats.
日本語の概要は準備中です。原文の説明を表示しています。
Passive, pattern-calibrated risk discovery for authorized security research over an open-source project, repository URL, dependency, release, or local checkout. Use when the security research agent needs to find highest-risk areas, map attack surface, identify likely bug-hunting targets, prioritize security review, inspect structural/logical/security-critical code, compare vulnerable versus patched versions, reason from broad high-severity vulnerability families, or remember areas of interest for later attack-chain research.
日本語の概要は準備中です。原文の説明を表示しています。
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.
日本語の概要は準備中です。原文の説明を表示しています。
Determines whether an adult patient meets eligibility criteria for initiating gender-affirming hormone therapy. Triggered when an adult patient requests gender-affirming hormones or presents for evaluation of hormone therapy eligibility.
日本語の概要は準備中です。原文の説明を表示しています。
Determines if a patient has completed ≥1 year of consistent and compliant hormone therapy for genital surgery approval. Triggers include patient requesting genital surgery and being on hormone therapy.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether commonly-excluded patients (eating disorders, elderly ≥75, upper GI disease) can actually receive a GLP-1 receptor agonist. Use when a clinician asks "can I give semaglutide to a patient with binge eating disorder / anorexia / bulimia", "is liraglutide safe in an 80-year-old", "GLP-1 with GERD or chronic gastritis", "GLP-1 in sarcopenic elderly", or anytime a patient is being ruled out for GLP-1 therapy based on a perceived contraindication. Grounded in Gorgojo-Martínez 2023 §6 (Myths or Reality).
日本語の概要は準備中です。原文の説明を表示しています。
Determines if patient meets criteria for genital gender-affirming surgery affecting fertility. Triggers include patient on hormones, considering surgery.
日本語の概要は準備中です。原文の説明を表示しています。
Determines whether bone mineral density (BMD) measurement is indicated when patients have osteoporosis risk factors or have discontinued sex hormone therapy following gonadectomy. Clinical triggers include documented osteoporosis risk factors (e.g., low body weight, glucocorticoid use, prior fracture) or cessation of sex hormone therapy after surgical gonadectomy.
日本語の概要は準備中です。原文の説明を表示しています。
Determines if adolescent meets criteria for GnRH agonist treatment to suppress pubertal development. Triggers include adolescent requesting to suppress puberty, adolescent with gender dysphoria seeking pubertal blockade, or clinician noting Tanner G2/B2 with request for hormone suppression.
日本語の概要は準備中です。原文の説明を表示しています。