4,682 件 ・ 関連度順
概要と使いどころ
Start-of-session situational report for a research or code repository. Reads the handoff, log, or status files the project actually keeps, checks live git state, and reports the objective, verified baseline, open tasks, blockers, and next actions, flagging where the documents and the repository disagree. Use when resuming work after time away or before changing anything. Its end-of-session twin is finished.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a whole deliverable (talk, course module, paper, chapter, or referee report) against its manifest without rewriting it. Runs a deterministic gate for build, citations, numbers, facts, and leaks and stops on failure, then runs a finder over each section and a strong-model pass over the whole work, and adjudicates into checks/<date>/findings.json and report.md with anchored findings, severities, and honest NOT CHECKED coverage within a dollar budget. Use when asked to lint or review the whole talk, module, or paper, for a pre-ship review, or for the night shift. Revision stays serial and author-led.
日本語の概要は準備中です。原文の説明を表示しています。
Runs several language models as independent coders on one labeling or discovery task and treats disagreement as data. Covers diverse panel assembly, independent voting, consensus rules, Cohen’s and Fleiss kappa, Krippendorff’s alpha, correlated-error limits on validity claims, human validation, and reporting. Use when the user asks about a council, panel, ensemble, or jury of models, how to combine model labels, or what kappa or alpha to report for model coders. Single-model codebook and validation work goes to text-classification, per-item confidence to llm-calibration-logprobs.
日本語の概要は準備中です。原文の説明を表示しています。
Runs several language models as independent coders on the same labeling or discovery task and reads their disagreement as data — panel assembly for model diversity, keeping votes independent, consensus rules, agreement statistics (Cohen's and Fleiss kappa, Krippendorff's alpha), the correlated-errors caveat that stops agreement being mistaken for validity, human validation beyond the panel, and reporting. Use when the user asks about a council, panel, ensemble, or jury of models, asks how to combine several models' labels, or asks what kappa or alpha to report for model coders. Single-model codebook and validation work goes to text-classification, per-item confidence to llm-calibration-logprobs.
日本語の概要は準備中です。原文の説明を表示しています。
Launches and configures the standalone presubmit CLI, an API-driven adversarial peer-review pipeline with 30-plus stages, including Red Team finders, Blue Team defence, verification cascade, legal pass, and copyedit, producing one consolidated report on disk. Verifies installation and API key, chooses the output location and smoke, standard, or custom mode, launches the run, and reports the result path. Use when the user asks to run presubmit, wants a deep unattended pre-submission audit, or needs a math or replication-code audit. Everyday self-audits go to paper-review-lite, and external refereeing to journal-review.
日本語の概要は準備中です。原文の説明を表示しています。
Designs multi-country survey experiments, covering case selection with a stated comparative logic, instrument localization and TRAPD translation, stimulus calibration, per-country power, and pooled versus per-country analysis with measurement-equivalence checks. Use when the user fields the same experiment in several countries, asks which countries to include, how to adapt an instrument without breaking comparability, whether to pool, or how large each country sample must be. Question wording goes to survey-design, reporting to methods-reporting, the study plan to pre-registration-writing.
日本語の概要は準備中です。原文の説明を表示しています。
Start-of-session report on where a repository stands. Reads the project's own handoff and log files, checks live git state, and reports objective, verified baseline, open tasks, blockers, and next actions. Use when resuming work. Twin of finished.
日本語の概要は準備中です。原文の説明を表示しています。
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
Earnings analysis — pre- and post-earnings. Pre-earnings preview: prior-guidance review, recent-events tracking, last call's Q&A, and a key-things-to-watch framework for an upcoming release. Post-earnings: two tiers — a fast in-chat summary card (default) and a full Markdown research report (on request). Covers beat/miss, segments, margins, guidance, estimates, valuation. US / HK / A-share. Use whenever the user wants an earnings preview or a post-earnings / quarterly-results writeup. Triggers: "earnings update", "quarterly results", "Q1/Q2/Q3/Q4 results", "earnings report", "post-earnings analysis", "beat/miss", "guidance update", "earnings preview", "pre-earnings", "what to watch this earnings", "before earnings", "财报分析", "业绩更新", "季度业绩", "季报", "年报", "盈利分析", "财报点评", "财报前瞻", "业绩前瞻", "财报预览", "上季度指引", "財報分析", "業績更新", "季度業績", "季報", "年報", "財報點評", "財報前瞻", "業績前瞻", "財報預覽".
日本語の概要は準備中です。原文の説明を表示しています。
Latest news articles, regulatory filings, community discussion topics for listed stocks, and SEC EDGAR filing analysis (10-K/10-Q/8-K/proxy/Form 4) via Longbridge. Triggers: "新闻", "公告", "资讯", "话题", "社区讨论", "SEC", "10-K", "10-Q", "8-K", "Form 4", "新聞", "公告", "資訊", "話題", "社區討論", "news", "filing", "announcement", "topic", "community", "SEC filing", "annual report", "quarterly report", "proxy", "insider filing", "regulatory rules", "监管规则", "涨跌停", "漲跌停", "T+1", "PDT rule", "熔断", "熔斷", "circuit breaker", "margin rules", "保证金", "保證金", "監管規則"
日本語の概要は準備中です。原文の説明を表示しています。
Generate markdown reports from issues. Filter by type, priority, epic, date range. Supports summary, detailed, progress, completion, velocity, and backlog analysis views.
日本語の概要は準備中です。原文の説明を表示しています。
Full-coverage formatted Excel report generation with Dutch market compatibility
日本語の概要は準備中です。原文の説明を表示しています。
Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate a broad Incan review using specialized reviewer roles, parallel slice reports, and a canonical merged review report. Use when the user asks for delegated review, multi-agent review, or when a broad dirty worktree should be reviewed by specialized passes rather than one generic reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize the currently staged Git changes as a human-readable, intent-grouped narrative. Use when the user wants a concise and brief report of what changed and why. Optionally can check the diff for intent coherence and show a risk and blast radius report.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem results for a Ruff PR from a PR number, PR URL, GitHub ecosystem-results comment, or detailed HTML report.
日本語の概要は準備中です。原文の説明を表示しています。
Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the `@claude` CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what to leave for the actual review. Report-only — does not edit files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "review bugs", "/review-bugs", "pull new bugs", "what was reported in Bugs", "update the bug list", or asks for an auto-review of reported bugs. Pulls the new messages from the Voxt Bugs and Bugs (Mobile) chats, turns them into entries in docs/bugs.md, reconciles the list with GitHub issues, pull requests and dev commits, moves finished bugs to docs/bugs-closed.md, and lists what needs a human decision.
日本語の概要は準備中です。原文の説明を表示しています。
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
日本語の概要は準備中です。原文の説明を表示しています。
输出测试结论 / 给上线决策时使用。适用于版本发布报告、阶段总结、缺陷分析。融合 ISTQB Test Summary Report、覆盖率分析、缺陷分布。
日本語の概要は準備中です。原文の説明を表示しています。
Generate project status reports (single or all projects)
日本語の概要は準備中です。原文の説明を表示しています。
Create polished single-file HTML artifacts for plans, reports, explainers, code reviews, lightweight dashboards, prototypes, and one-off editing tools. Use when the user asks for a standalone HTML file, single HTML, HTML artifact, interactive report, shareable local artifact, Alpine.js artifact, custom CSS artifact, copy/export UI, or a browser-openable deliverable instead of Markdown.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。