1,756 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "update the changelog", "add a changelog entry", "write a CHANGELOG entry", or when preparing a git commit in StreamFlow that requires updating the `## [Unreleased]` section of `CHANGELOG.md`.
日本語の概要は準備中です。原文の説明を表示しています。
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
日本語の概要は準備中です。原文の説明を表示しています。
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace. Covers adding new content, updating plugin.json, validation, and release tagging.
日本語の概要は準備中です。原文の説明を表示しています。
Modern .NET project structure including .slnx solution format, Directory.Build.props, central package management, SourceLink, version management with RELEASE_NOTES.md, and SDK pinning with global.json.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds or audits a social-science replication package and evaluates the manuscript and archived research objects against FAIR principles. Scaffold mode writes the folder structure, README, master.R, figure-table crosswalk, codebook, LICENSE placeholder, and .gitignore; audit mode grades the package against a pre-release checklist and audits data, code, materials, identifiers, licenses, access restrictions, and availability statements. Use when setting up or repairing a package, checking one before submission, auditing FAIR compliance, or drafting availability statements. Adapted from Yusaku Horiuchi’s replication-package-guide.
日本語の概要は準備中です。原文の説明を表示しています。
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", "财报分析", "业绩更新", "季度业绩", "季报", "年报", "盈利分析", "财报点评", "财报前瞻", "业绩前瞻", "财报预览", "上季度指引", "財報分析", "業績更新", "季度業績", "季報", "年報", "財報點評", "財報前瞻", "業績前瞻", "財報預覽".
日本語の概要は準備中です。原文の説明を表示しています。
Start an authorised Anabasis v2 campaign through its one command, which asks the log before each move whether the move can report anything, or stop a named run and release what it held. Use when the operator asks to start, launch, resume or stop a campaign or a run, to check whether a campaign is ready for its next move, or why a move was refused. Owns the start and the stop; run-improvement-campaign reads the table, and whole-run-investigation reads what a run did.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user wants to find, shortlist, vet, or enrich US public-relations and communications agencies — media relations, crisis comms, investor relations (IR), product-launch PR, tech/startup PR, healthcare PR, B2B PR, public affairs, brand reputation, and internal communications. Triggers on "find me a tech PR agency in NY", "shortlist three IR firms for our IPO", "we need crisis comms help for a brand reputation issue", or "pull contact info for these 10 PR firm domains", even when described indirectly (we need press, get us into TechCrunch, manage our brand reputation). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer to find-marketing-agency when scope is broader marketing beyond PR/comms. Skip in-house PR/comms hires, "write me a press release" DIY asks, PR-software comparisons (Cision, Muck Rack), influencer-marketplace questions, non-US firms, individual freelance PR people.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Finds or publishes a pkg.pr.new canary release for a Storybook branch. Use when the user wants the canary package specifier for a branch or needs to trigger the canary workflow manually.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to map or analyze flows, pipelines, processes, or sequences of events in this repo — e.g. "mapa el flujo", "flow", "pipeline", "ciclo de vida", "trace the request", "how does the build/release flow work", "diagrama del flujo". Maps data flows, request lifecycles, CI/CD pipelines, and state transitions with verified file:line evidence. Distinct from analyze-code (which maps code structure); this skill maps movement over time.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to validate the plugin, check integrity, verify cross-references, or before a release. Also use when the user says 'validate', 'check plugin', or 'verify'.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and produce a complete product launch marketing package — landing page copy, email sequences, ad campaigns, press release, social posts, and launch timeline. Orchestrates all other kai skills into a coordinated launch. Use when "product launch", "launch campaign", "go-to-market", "GTM plan", "launch marketing", "we're launching", "prepare launch materials", or any request to coordinate marketing for a new product, feature, or major update.
日本語の概要は準備中です。原文の説明を表示しています。
发布说明编写时使用。适用于 Changelog / 迁移指南 / 影响说明。
日本語の概要は準備中です。原文の説明を表示しています。
设计发布策略时使用。适用于灰度 / 蓝绿 / 金丝雀 / 滚动更新 / 回滚方案。融合 Progressive Delivery + Feature Flags + 自动回滚。
日本語の概要は準備中です。原文の説明を表示しています。
Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.
日本語の概要は準備中です。原文の説明を表示しています。
wacrawl: WhatsApp Desktop archive import/search, slices, backups, repo/release work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up deployment infrastructure or enforcing a gated release path. Routes to deploy gates, setup, or rollback based on the current deployment stage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's commits follow (or mostly follow) Conventional Commits and a mechanically-accurate section breakdown beats a model's reading of the diff.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a plain-language idea into a tested Chrome Manifest V3 extension, release bundle, store materials, and a resumable launch workflow using Codex skills and Playwright MCP acceptance checks.
日本語の概要は準備中です。原文の説明を表示しています。
Scan Python requirements and environments for known vulnerable or malicious packages before they move further through delivery or promotion workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a license inventory for Go module dependencies before release, procurement review, or open-source due diligence.
日本語の概要は準備中です。原文の説明を表示しています。
Answer Aperture Wallet questions from first-party product, security, network, release, app-screen, and Journal sources while enforcing explicit wallet-secret and no-transaction safety boundaries.
日本語の概要は準備中です。原文の説明を表示しています。