1,334 件 ・ 関連度順
概要と使いどころ
Coordinates credit monitoring and identity theft protection services for individuals affected by a data breach. Covers vendor selection criteria, enrollment logistics, coverage duration (12-24 months), identity theft insurance options, communication to affected individuals, and enrollment rate tracking. Keywords: credit monitoring, identity protection, breach response, Experian, enrollment, identity theft insurance.
日本語の概要は準備中です。原文の説明を表示しています。
Review aviation insurance coverage and requirements. TRIGGERS - Use when user needs help with aviation-insurance-review related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Compare auto insurance options with coverage analysis. TRIGGERS - Use when user needs help with auto-insurance-comparison related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates health insurance plan structures with actuarial value, network analysis, and cost projection. Use when analyzing health plans, comparing coverage, or projecting healthcare costs.
日本語の概要は準備中です。原文の説明を表示しています。
Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".
日本語の概要は準備中です。原文の説明を表示しています。
Audit guardrail coverage — bypass vectors, false positive rates, policy gap analysis, red-team scenarios. Use when asked to "audit our AI guardrails", "can our filters be bypassed", or "check guardrail false positives".
日本語の概要は準備中です。原文の説明を表示しています。
Integrate API quality gates into CI — linting, breaking change detection, and coverage checks. Use when asked to "add API checks to CI", "detect breaking changes in CI", or "set up an API quality gate".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing cloud cost controls — tagging coverage, alerting, and FinOps maturity. Use when asked to "audit our cost controls", "is our tagging complete", or "assess our FinOps maturity".
日本語の概要は準備中です。原文の説明を表示しています。
PR & Community engineer — press pitches, social media, open source community, DevRel, and coordinated launch moments. Use when asked to "write a press release", "plan a launch", "build a community", "draft a HN or Twitter post", or "get media coverage".
日本語の概要は準備中です。原文の説明を表示しています。
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
日本語の概要は準備中です。原文の説明を表示しています。
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".
日本語の概要は準備中です。原文の説明を表示しています。
Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".
日本語の概要は準備中です。原文の説明を表示しています。
Generates unit tests for command and query handlers using xUnit and NSubstitute. Implements Arrange-Act-Assert pattern with comprehensive test coverage for success and failure scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether the documentation in src/site/markdown/ adequately covers the Java SDK functionality.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze upstream specs (agentskills.io, Claude Code plugin/marketplace format, OpenAI Codex plugins/marketplace, OpenClaw, MCP and MCP Registry, CodeRabbit, APM) for changes, identify gaps in skillsaw's rule coverage, and create or update PRs to close those gaps. Use when performing periodic maintenance on the skillsaw linter.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare your codebase for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates comprehensive documentation (flowcharts, user stories, inline comments). (project, gitignored)
日本語の概要は準備中です。原文の説明を表示しています。
Summarize a supplied URL from fetched content with source locations, acquisition coverage and explicit access failures. Use for articles, documentation, API references and web pages; preserve version, author attribution and uncertainty in the requested output format.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate multiple source findings into an attributed synthesis or comparison. Use for combine these summaries, synthesize results, merge findings or multi-source analysis. Preserve claim-level provenance, coverage, qualifiers, conflicts and uncertainty rather than repeatedly compressing narrative summaries.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests to summarize files, URLs, images, inline text, or multiple sources. Select the requested format and preserve evidence, exact counts, uncertainty and source coverage through summarization, synthesis and agent-result relay.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the primary outcome is comparing documentation claims with implementation evidence, synchronizing docs from verified changes, or freshness review, including drift, missing coverage, stale claims, and post-change updates.
日本語の概要は準備中です。原文の説明を表示しています。
Configures pyproject.toml and Python packaging using PEP 517/518/621/660/723 standards. Use when creating or updating pyproject.toml, selecting a build backend (hatchling/setuptools/flit), configuring ruff, ty, mypy, pytest, or coverage tool sections, setting up dependency constraints or optional extras, defining CLI entry points, configuring pre-commit hooks, establishing src-layout directory structure, or preparing a package for PyPI publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Executes a four-phase feature addition workflow (Discovery, Planning, TDD Implementation, Verification) for Python projects. Use when adding a new feature end-to-end — discovering project structure and integration points, drafting a feature spec with MoSCoW-prioritized requirements and BDD acceptance criteria, implementing via test-first TDD cycles, then verifying with ruff lint, ty type checks, and behavior-focused regression and contract coverage.
日本語の概要は準備中です。原文の説明を表示しています。