4,911 件 ・ 関連度順
概要と使いどころ
Turn vulnerability notes, disclosure reports, PoCs, source code, or Codex Security findings into self-contained, sceptically validated, natural-sounding vulnerability reports. Use for one vulnerability or a disclosure campaign; a Codex Security scan is optional.
日本語の概要は準備中です。原文の説明を表示しています。
Run clippy locally and report only issues in the current diff, matching the CI reviewdog flow. Use when asked how to lint changed code or get clippy feedback on a branch before pushing.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a concise, structured analysis report of a codebase: dependencies, workflow, and context.
日本語の概要は準備中です。原文の説明を表示しています。
Research a topic to support a decision, three ways: draft a research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), turn a finished research report into a short summary with cited sources that other skills can use directly, or run the research here with parallel web searches. Built-in research types: market, domain, technical, competitive, user-voice, academic-lit; also supports choosing between candidates, and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between"
日本語の概要は準備中です。原文の説明を表示しています。
Produce a structured codebase analysis report with architecture overview, critical files, patterns, and actionable recommendations. Use when asked to "analyze codebase", "explore codebase", "understand this codebase", "map the codebase", "give me an overview of this project", "what does this codebase do", "codebase report", "project analysis", "audit this codebase", or "how is this project structured".
日本語の概要は準備中です。原文の説明を表示しています。
Structures portfolio company monitoring with monthly financial packages, KPI dashboards, and management assessment frameworks. Use when monitoring portfolio companies, building reporting templates, or tracking financial performance.
日本語の概要は準備中です。原文の説明を表示しています。
Structures Regulation AB II compliance with asset-level data requirements, servicer reporting, and shelf registration eligibility. Use when ensuring Reg AB compliance, preparing ABS reporting, or structuring shelf eligibility.
日本語の概要は準備中です。原文の説明を表示しています。
Triage the content corpus against the latest GSC snapshot and produce a prioritized refresh report. Read-only: reports, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Write Bugcrowd-format reports — VRT (Vulnerability Rating Taxonomy) mapping, P1-P5 severity, impact-led writing, and Bugcrowd-specific submission etiquette. Use AFTER triage-validation passes for Bugcrowd programs.
日本語の概要は準備中です。原文の説明を表示しています。
Write production-grade HackerOne reports — title formula, impact-led writing, CVSS 3.1 scoring, complete PoC formatting, attached files, and submission etiquette. Use AFTER triage-validation passes and you're ready to submit on HackerOne.
日本語の概要は準備中です。原文の説明を表示しています。
Validate a bug bounty finding before writing a report — the 7-Question Gate, 4 pre-submission gates, always-rejected list, conditional chain table, CVSS 3.1 quick reference, and severity decision guide. Use BEFORE writing any report to avoid N/A and low quality submissions.
日本語の概要は準備中です。原文の説明を表示しています。
Report ground-truth Claude token consumption and estimated cost by parsing JSONL session files directly. Use when checking API spend, auditing token usage by project/session/model, generating daily/weekly/monthly cost reports, or diagnosing ccusage undercounting. Includes subagent files that ccusage ignores.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, responsive design, theming, and anti-patterns. Generate a scored report with P0-P3 severity ratings. Report-only — documents issues for other skills to fix. Triggers on audit the design, check accessibility, technical review, performance audit, a11y check.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a person in systematic observation of systems, patterns, or phenomena. AI coaches neutral attention, field notes methodology, pattern recognition, hypothesis formation, and structured reporting for debugging, research, and system understanding. Use when a person wants to understand a system's behavior before intervening, when someone keeps jumping to conclusions and needs the discipline of observation first, when preparing an evidence-based report, or when studying team dynamics or process effectiveness through direct observation.
日本語の概要は準備中です。原文の説明を表示しています。
Design terminal output for a CLI tool with chalk colors, Unicode glyphs, multiple verbosity levels (human, verbose, quiet, JSON), and consistent voice rules. Covers color palette selection, status indicator design, reporter function architecture, ceremony/narrative output variants, and cross-terminal compatibility. Use when building a new CLI reporter module, adding warm narrative output to an existing tool, standardizing output across multiple commands, or designing machine-readable JSON alongside human-readable text.
日本語の概要は準備中です。原文の説明を表示しています。
Triage maintenance problems by severity, document findings with context, route to appropriate specialist agent or human, and create actionable issue reports. Use when a maintenance task encounters problems beyond automated cleanup: code that is unsafe to delete, configuration changes requiring domain expertise, breaking changes detected during cleanup, complex refactoring needed, or security-sensitive findings such as hardcoded secrets or vulnerabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only audit of a GitHub repository's security posture. Gathers ref protection (rulesets AND classic branch protection), Actions token permissions, code and supply-chain features (Dependabot, secret scanning, push protection, CodeQL), and repo hygiene toggles via `gh api`, then classifies findings against essential / recommended / advanced tiers into a PASS/GAP report. Makes NO changes. Use when reviewing a repo before open-sourcing or a release, auditing a public user-owned repo whose CI auto-commits to the default branch, verifying a hardening change actually took effect, or producing a baseline security posture report for a repository.
日本語の概要は準備中です。原文の説明を表示しています。
Report where a session missed moo's standard — the agent asks only while stating intent and shape, then works on its own — as issues a builder can act on. Pass a session id to report on a past session instead of this one.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch upcoming economic events and data releases using FMP API. Retrieve scheduled central bank decisions, employment reports, inflation data, GDP releases, and other market-moving economic indicators for specified date ranges (default: next 7 days). Output chronological markdown reports with impact assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive US stock analysis including fundamental analysis (financial metrics, business quality, valuation), technical analysis (indicators, chart patterns, support/resistance), stock comparisons, and investment report generation. Use when user requests analysis of US stock tickers (e.g., "analyze AAPL", "compare TSLA vs NVDA", "give me a report on Microsoft"), evaluation of financial metrics, technical chart analysis, or investment recommendations for American stocks.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive market environment analysis and reporting tool. Analyzes global markets including US, European, Asian markets, forex, commodities, and economic indicators. Provides risk-on/risk-off assessment, sector analysis, and technical indicator interpretation. Triggers on keywords like market analysis, market environment, global markets, trading environment, market conditions, investment climate, market sentiment, forex analysis, stock market analysis, 相場環境, 市場分析, マーケット状況, 投資環境.
Generate professional reports from analysis results. Use when user needs to create formatted documents summarizing findings.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.
日本語の概要は準備中です。原文の説明を表示しています。