3,040 件 ・ 関連度順
概要と使いどころ
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.
日本語の概要は準備中です。原文の説明を表示しています。
Generate value proposition statements for marketing, sales, and onboarding from existing value propositions. Use when writing marketing copy, creating sales messaging, or crafting onboarding messages.
日本語の概要は準備中です。原文の説明を表示しています。
Brainstorm product positioning ideas differentiated from competitors. Identifies top competitors and generates positioning statements with rationale. Use when developing product positioning, differentiating from competitors, or crafting brand positioning strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
日本語の概要は準備中です。原文の説明を表示しています。
Draft launch or promotion copy for a shipped feature.
日本語の概要は準備中です。原文の説明を表示しています。
Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
日本語の概要は準備中です。原文の説明を表示しています。
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
日本語の概要は準備中です。原文の説明を表示しています。
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a post-tag NemoClaw Announcement from the verified release range and shipped PRs. Use when summarizing a release.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.
日本語の概要は準備中です。原文の説明を表示しています。
Capture decisions and commitments after a meeting and draft a concise follow-up.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate and review evidence-backed workflows with Screenpipe tools and shared drafts.
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct a customer relationship from recorded interactions before answering or drafting a response.
日本語の概要は準備中です。原文の説明を表示しています。
Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Security Command Center on Google Cloud. Use when retrieving details for a security finding by its name, validating finding scope (e.g., verifying findingClass is TOXIC_COMBINATION, VULNERABILITY, EXTERNAL_EXPOSURE, or THREAT), or fetching finding details for triage. Don't use to draft remediations, apply patches, or execute configurations.
日本語の概要は準備中です。原文の説明を表示しています。
Design-for-manufacturing review of a part for sheet metal, CNC machining, or injection molding - bends, reliefs and flat patterns; machining access, internal corners, deep features and setups; draft, undercuts and projected area. Use when the user asks whether a part can be bent, machined or molded, asks about manufacturability or tooling, or asks for a DFM review or redesign.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly QBR-prep runbook. Finds every account whose next QBR falls within {{lookahead_days}} days of HubSpot's {{qbr_date_property}} field, pulls usage trends from Postgres and account/CSM data from HubSpot, and assembles a draft deck plus a briefing doc under {{decks_folder}} — read-only across every source system.
日本語の概要は準備中です。原文の説明を表示しています。
Daily runbook for tracking new customer accounts against onboarding milestones in Postgres and HubSpot for {{projectName}}. Covers the milestone framework, stall and overdue detection, nudge drafting, the owning-CSM alert, and the human approval gate before anything sends or changes account state.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly reusable-session ticket-to-KB loop. Reads recently resolved Plain threads, clusters them into recurring topics, cross-references {{kb_path}} of {{kb_repo}} and a durable ledger to find topics with real volume and no article, drafts the top gaps from the actual resolutions, and opens a PR only — never publishing or merging.
日本語の概要は準備中です。原文の説明を表示しています。
Runbook for turning a new HubSpot lead in {{hubspot_list}} into a researched, personalized outbound sequence for {{projectName}}. Covers enrichment research, the outreach playbook (angles, proof points, what to avoid), sequence drafting, HubSpot logging, the daily cap, and the human approval gate before anything sends.
日本語の概要は準備中です。原文の説明を表示しています。
Daily outbound-sourcing sweep for {{greenhouse_role}}. Searches LinkedIn for candidates matching {{sourcing_criteria}}, dedupes every match against the role's Greenhouse pipeline, and drafts a personalized outreach email per new candidate to {{recruiter_review_inbox}} — capped at {{daily_cap}} per run. Never sends outreach and never writes to Greenhouse; the recruiter reviews, sends, and owns the ATS.
日本語の概要は準備中です。原文の説明を表示しています。