4,299 件 ・ 関連度順
概要と使いどころ
Evaluates proxy fight mechanics with shareholder base analysis, ISS/Glass Lewis recommendations, and vote probability modeling. Use when analyzing proxy contests, assessing vote outcomes, or evaluating director nomination campaigns.
日本語の概要は準備中です。原文の説明を表示しています。
Component type definitions, settings schemas, directory patterns, and validation rules for the fullstack-typescript tech pack.
日本語の概要は準備中です。原文の説明を表示しています。
Manage tasks and plans using the .tasks/ directory.
日本語の概要は準備中です。原文の説明を表示しています。
Design and build cinematic websites, interactive portfolios, product stories, and real-time 3D experiences with subject-specific art direction and scroll choreography. Use for new builds, redesigns, motion improvements, scroll audits, or storyboards in standalone HTML and existing apps; includes responsive, reduced-motion, and static fallbacks. Not for ordinary dashboards or unrelated animation.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt full Account Takeover (ATO) by chaining lower-severity findings — IDOR-to-email-disclosure, password-reset-token-theft, OAuth-redirect-uri abuse, response-manipulation, cookie scope, CRLF in Set-Cookie, race-condition on signup. Use when the user wants to escalate small findings to ATO or thinks an ATO path exists.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt OAuth 2.0 and OIDC flaws — redirect_uri abuse, state CSRF, PKCE bypass, scope manipulation, implicit-flow token theft, postMessage origin tricks, ID token sub claim swap, JWKS confusion, response_type confusion, and OAuth-CSRF. Use when an app has Google/GitHub/Facebook/Apple/custom OAuth or OpenID Connect.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt Insecure Direct Object Reference (IDOR) — test horizontal and vertical privilege escalation across user IDs, org IDs, tenant boundaries, and unguessable identifiers. Use when the user has an API endpoint with an identifier in the path/body that may be tested for unauthorized cross-user access.
日本語の概要は準備中です。原文の説明を表示しています。
Fuzz directories, files, and parameters using ffuf, feroxbuster, arjun, paramspider, and x8. Use when the user has live hosts and needs to find hidden routes, backup files, exposed configs, and untracked URL parameters.
日本語の概要は準備中です。原文の説明を表示しています。
Operating guide for construction project documents — load before reading drawings, specs, schedules, RFIs, submittals or bids. Data-access rules (never read PDFs directly; rasterize first), AgentCM graph-guided vision, drawing and cross-reference conventions, document precedence. Triggers: 'construction project', 'drawings', 'specs', 'sheet', 'RFI', 'submittal'.
日本語の概要は準備中です。原文の説明を表示しています。
Copy this repo's skills into another agent harness's skills directory by name — resolves the harness alias to its path via scripts/sync-targets.json and runs sync-skills.sh. Use only when the user asks to copy/sync/push the skills to another harness (oh-my-pi, opencode, kimi, codex, etc.) — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Bring every per-repo open-pr config below the current directory up to the schema this build expects. Use after updating the plugin, or when a command reports a config too old. Takes no URL.
日本語の概要は準備中です。原文の説明を表示しています。
Create isolated git worktrees with smart directory selection and safety verification
日本語の概要は準備中です。原文の説明を表示しています。
Gather and persist project design context such as audience, brand personality, UX goals, and implementation defaults for future better-web-ui work. Use when starting a project, defining UI direction, or establishing reusable design guidance before other better-web-ui skills.
日本語の概要は準備中です。原文の説明を表示しています。
Ripgrep-powered dead-code crawler that finds stale, broken, or orphaned JavaScript/CJS/MJS modules in the Agent Studio framework. Walks a target directory, checks each file for external references, and surfaces (or deletes) unreferenced files. Prevents registry bloat and silent tool dropouts from modules no one calls.
日本語の概要は準備中です。原文の説明を表示しています。
Next.js 16 caching model expertise covering the 'use cache' directive, cacheLife() API, cacheTag() for invalidation, cacheComponents configuration, and Partial Prerendering (PPR). Use when implementing caching strategies in Next.js 16+ applications, migrating from unstable_cache, or optimizing server component rendering.
日本語の概要は準備中です。原文の説明を表示しています。
Focuses on routing, CSRF protection, context handling, and template usage within the internal handlers directory.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade web interfaces with intentional aesthetic direction. Avoids generic AI aesthetics (centered layouts, Inter/Arial, purple gradients, uniform corners). Use for UI components, dashboards, landing pages, React/HTML/CSS layouts where design quality matters.
日本語の概要は準備中です。原文の説明を表示しています。
Deeply analyzes Agent Studio framework structural health: catching phantom require() references, wrong module depth paths, missing skill/agent dependencies, bloated configurations, archived references in active code, stale catalog counts, and empty tool/skill directories.
日本語の概要は準備中です。原文の説明を表示しています。
Search and retrieve academic papers from arXiv.org using WebFetch and Exa. No MCP server required - uses existing tools to access arXiv API directly.
日本語の概要は準備中です。原文の説明を表示しています。
Package source files into plugin directories using release-mapping.yaml. Use when preparing a plugin release.
日本語の概要は準備中です。原文の説明を表示しています。
Initialise a project for knowledge base use. Appends the [Knowledge Base] section to the project's CLAUDE.md, creates the library/ directory structure, optionally seeds with three example library files from the Agentic SDLC research, and reports next steps. Run once after installing sdlc-knowledge-base.
日本語の概要は準備中です。原文の説明を表示しています。
Run the SDLC validation pipeline using direct tool invocations. No wrapper scripts required. Use when checking code quality before commits or PRs.
日本語の概要は準備中です。原文の説明を表示しています。
Complete App Store Optimization toolkit - generate metadata in any language, analyze competitors, optimize keywords, set up IAPs/subscriptions, and submit to App Store Connect via direct API
日本語の概要は準備中です。原文の説明を表示しています。
Used when the user asks to "create slides", "make a presentation", "build a deck", "design slides", "generate a pitch deck", "create a conference talk", "make a keynote", "presentation design", "slide layout", "slide template", "presentation structure", or mentions slides, presentations, decks, or talks in any context. Also triggers when the user wants to plan the content and visual direction of a presentation before generating it. This is the entry-point orchestrator that drives the full slide creation workflow across both HTML and PPTX formats. Examples: "I need to create slides for my conference talk about AI adoption", "can you turn this markdown into a presentation?", "I have a product demo tomorrow and need visual materials", "convert my existing PowerPoint to interactive HTML slides".
日本語の概要は準備中です。原文の説明を表示しています。