3.8万 件 ・ 関連度順
概要と使いどころ
Legal precedent App-in-Skill (Busabase-backed) desk for internal casebase search, local court-pattern analysis, similar-case packs, citations, and approval-gated research exports. Use when the user invokes $kelly-legal-precedent-desk, mentions 类案检索, 本地裁判尺度, 内部案例库查询, 案例查阅与收藏, precedent research, similar cases, legal research pack, or wants a Busabase-backed desk where lawyers review agent-prepared precedent findings before reuse.
日本語の概要は準備中です。原文の説明を表示しています。
Build, maintain, and run conformance tests for canonical App-in-Skill projects created by kelly-app-skill-creator. Use when a Kelly app skill needs contract checks, local server smoke tests, responsive browser acceptance, temporary open-source Busabase integration, environment-gated Busabase Cloud OAuth verification, lazy provisioning checks, persistence tests, AirApp parity tests, or CI coverage. Keep app creation in kelly-app-skill-creator and own only the reusable test harness, per-skill fixtures, execution gates, diagnostics, and truthful pass/fail/skip reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Validates compliance, security, and GRC terminology in marketing copy. Enforces accurate claims, prevents common mistakes (e.g., calling SOC 2 a "certification"), and applies risk-first narrative framing for B2B SaaS audiences. Use when writing or reviewing any marketing content that references compliance frameworks, security standards, regulatory requirements, or audit processes. Also use when creating ads, landing pages, emails, case studies, or sales collateral for GRC/cybersecurity B2B SaaS products.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM program review. Also use when asked to "build an ABM program," "set up account-based marketing," "design a target account strategy," "plan ABM campaigns," or "measure ABM results." Designed for demand gen teams selling to Mid-Market companies with $10K-$50K+ ACV, multi-persona buying committees, and 3-6 month sales cycles.
日本語の概要は準備中です。原文の説明を表示しています。
Generates account research briefs, personalized outreach sequences, persona-specific talk tracks, and objection handling frameworks for B2B SaaS BDR teams. Use when preparing BDR outreach for target accounts, building prospecting sequences, creating call scripts, developing objection responses, onboarding new BDRs, or reviewing outreach performance. Also use when asked to "write outreach emails," "build a prospecting sequence," "create a call script," "handle objections," or "research an account for outreach." Designed for BDR teams selling compliance, security, and GRC platforms to mid-market and enterprise buyers with multi-persona buying committees.
日本語の概要は準備中です。原文の説明を表示しています。
Generates publish-ready LinkedIn posts for B2B SaaS marketing leaders writing from an operator point of view: real decisions, real trade-offs, real constraints, and defensible lessons. Use when turning an internal observation, framework, campaign decision, miss, or shipped artifact into a public LinkedIn post. Best for demand generation, ABM, marketing ops, product marketing, and SaaS GTM leaders building credibility through practical operating insight. Not intended for generic brand posts, company announcements, sales outreach, or long-form content.
日本語の概要は準備中です。原文の説明を表示しています。
Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire, standardizing campaign tracking, fixing broken lead routing, cleaning up HubSpot or CRM data, building QA checklists for campaign launches, or creating incident response procedures for marketing system failures. Also use when asked to "fix our UTM mess," "standardize campaign naming," "build a QA checklist," "audit our marketing ops," or "create an ops runbook." Designed for B2B SaaS marketing teams running HubSpot with multi-geo, multi-segment operations.
日本語の概要は準備中です。原文の説明を表示しています。
Generates and maintains competitive battlecards from win/loss data, competitor intel, G2 reviews, and sales feedback. Use when building battlecards for a specific competitor, updating existing battlecards with new intel, preparing BDRs or AEs for competitive deals, analyzing win/loss patterns against a competitor, or responding to a competitor's product launch or pricing change. Also use when asked to "build a battlecard," "update competitive intel," "how do we beat [competitor]," "what do we say when a prospect mentions [competitor]," or "analyze our win/loss against [competitor]." Designed for B2B SaaS teams selling against known competitors in deals with multi-persona buying committees.
日本語の概要は準備中です。原文の説明を表示しています。
Generates sourced, BDR-ready account research briefs for named target accounts in B2B SaaS ABM and outbound motions. Use after a target account list is built and before outreach sequences are written. Best for Tier 1, Tier 2, and intent-qualified accounts where BDRs need a clear "why this account, why now, why this persona" hypothesis. Designed for B2B SaaS teams selling compliance, security, GRC, risk, or other technical platforms into mid-market and enterprise buyers. Not intended for broad list building or mass enrichment.
日本語の概要は準備中です。原文の説明を表示しています。
Generates the monthly revenue-accountable marketing report that B2B SaaS marketing leaders deliver to CEOs, CFOs, executive teams, and boards. Use when preparing the monthly CEO report, drafting the marketing section of a board deck, defending budget decisions, diagnosing pipeline gaps, or transitioning marketing from MQL/SQO reporting to revenue, CAC payback, and forward pipeline coverage. Designed for B2B SaaS demand generation leaders who own pipeline targets across segments, geos, and motions, and need to explain marketing's revenue contribution in executive language.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a single deterministic Python script to harmonize units, create/update metadata, move files to output_data/, and clean up input_data/.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a company's economic moat, EBITA margin trajectory, and organic growth trajectory from analyst reports, earnings transcripts, or long-form articles. Produces structured qualitative outlook that feeds into the Financial Modeling skill's assumption generation.
日本語の概要は準備中です。原文の説明を表示しています。
Produces and audits externally published marketing copy where factual claims must survive scrutiny — landing pages, product pages, launch emails, one-pagers, search/social metadata. Every statistic, competitor comparison, capability description, and proof point is traced to a fetched source or the project's own documents, labeled, and adversarially verified before it ships. Use when writing or rewriting high-stakes marketing copy; when copy must pass legal, compliance, brand, or claims review; when the audience is skeptical technical or executive buyers; when the company has little or no customer proof yet (pre-launch, zero customers); or when auditing existing copy for unsupported claims, invented capabilities, unverified statistics, or AI-slop language.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when the user asks to crop, reframe, trim, or improve composition of still photos, especially selected event photos, album photos, portraits, speakers, panels, workshops, or group photos. Use after photo selection or correction when the task is composition improvement rather than selecting images.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when 01_intent/creative_brief.yaml and 03_analysis artifacts exist and the user asks to choose clips, extract candidate segments, run triage, or build 04_plan/selects_candidates.yaml. Use before /blueprint whenever selects are missing, and re-run when the brief or analysis changes.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when the user is setting up this project for the first time, when dependencies are missing, API keys are not configured, or when 'npm run demo' fails. Triggers on: 'セットアップ', '環境構築', 'setup', 'install', 'API key', 'ffmpeg not found', 'GEMINI_API_KEY', 'cannot find module'.
Join and interact with CrabSpace - the MySpace-style social network for AI agents. Use when creating a profile, customizing appearance, managing friends, or posting on comment walls. Handles registration, tweet verification, profile updates, and social features.
日本語の概要は準備中です。原文の説明を表示しています。
Manage GoClaw AI agent gateway servers from Claude Code. Use this skill when the user mentions "goclaw", "gateway server", "AI agent platform", or wants to execute shell commands remotely on a server, manage AI agents, approve agent actions, inspect chat sessions, or administer multi-tenant AI infrastructure. Wraps the `goclaw` CLI to call REST + WebSocket APIs of GoClaw Gateway.
日本語の概要は準備中です。原文の説明を表示しています。
当使用者说“这篇建模论文还能怎么提升”“按评分表排修改优先级”“时间不够先改什么”“给我一个论文改进清单”“要不要再加一个高级模型”时使用。基于现有草稿、模型工作包、批判 findings、评分规则和真实剩余资源建立可定位的 gap register，再按结论影响、评分关联、工作量、依赖与失败风险排序；每项写所需数据/代码/作者决定、验证与验收条件，先给一个最小可行修订，不用装饰复杂度替代证据，不编创新、实验或评委偏好。
日本語の概要は準備中です。原文の説明を表示しています。
当有一条推导、模型方程、标度律或最终公式，想在相信它之前先过最便宜的一关时使用。逐项查量纲：先统一记号、建符号量纲表，再按加减两侧同量纲、等式两边一致、指数对数三角函数的宗量无量纲逐条核对，指出第一处不一致；每个通过的项还要说出它代表什么物理贡献，说不出的项就是没理解的项。结论里写明量纲通过不等于物理正确。
日本語の概要は準備中です。原文の説明を表示しています。
当使用者说"把这几张照片拼成一页"、"拼成一张长图"、"这组照片排成一页 PDF"时使用。Arrange 3–9 finished photographs into a cohesive one-page series, contact sheet, long image, or PDF. Use when a user wants to sequence and present a photo set with consistent frames, gutters, and canvas treatment. Preserve the photographer's chosen order unless they explicitly ask for sequencing suggestions; do not infer artistic intent from pixels alone. For a publication or exhibition-board layout with bands, a lead photo per band and a credit per band, or more than 9 photos, use photo-spread-composer.
日本語の概要は準備中です。原文の説明を表示しています。
Design, refine, implement, or review application UI and user journeys with minimal controls, clear actions, shared components, realistic prototypes, and polished behavior. Use for product screens, forms, onboarding, navigation, settings, and chat/task interfaces; not backend-only work or general graphic design.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate why a defect or insufficiency was introduced and accepted by tracing code, pull requests, task context, and accessible development sessions. Use for second-order learning after a fix, blameless root-cause analysis, or preventing a recurring class of engineering mistakes.
日本語の概要は準備中です。原文の説明を表示しています。
Delegate independent research, implementation, or verification in parallel when it can save time after dispatch and review overhead, or when explicitly requested. Keep decisions and final integration in the main agent.
日本語の概要は準備中です。原文の説明を表示しています。