6.6万 件 ・ 関連度順
概要と使いどころ
Use claudraband CLI and daemon workflows programmatically to send prompts, resume sessions, inspect status, and manage live session state. Use when running, scripting, or automating Claude Code via claudraband/`cband`, including startup prompt handling, `--connect` daemon mode, and ACP sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Writes on-brand social media captions for SMBs. Takes post concepts or a content calendar and produces ready-to-post captions with hooks, body copy, CTAs, and hashtags. Reads brand-style.md for voice and tone. Supports Instagram, LinkedIn, Facebook, TikTok, and X. Batch and single-post modes. Optional trend and competitor research via Firecrawl and SerpApi.
日本語の概要は準備中です。原文の説明を表示しています。
Use for writing, reviewing, debugging, or testing Pandera schemas and runtime validation for Polars DataFrame or LazyFrame pipelines installed with pandera[polars]. Trigger on pandera.polars DataFrameSchema, DataFrameModel, Column, Field, Check, PolarsData, decorators, coercion, strictness, lazy error collection, and validation-depth decisions. Do not use for pandas-backed Pandera, Pydantic object models, Polars transformations without Pandera, static dataframe typing alone, or generic data-quality platforms.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Computer Vision Scientist. Use when a task calls for Computer Vision Scientist judgment. Reasons from image formation, projective geometry (pinhole intrinsics and extrinsics, epipolar/PnP/bundle adjustment, similarity-scale ambiguity), and COCO/LVIS AP mechanics through DINOv3/SigLIP 2 foundation baselines, RF-DETR/YOLO26/SAM 3 models, COLMAP 4/GLOMAP and VGGT geometry, pycocotools/TrackEval/BOP evaluation, and CVPR reporting and EU AI Act limits while treating train–test and pretraining leakage, AP evaluation-setting gaming, preprocessing mismatches (EXIF, BGR, aliased resizing), label noise, and camera-convention and scale errors as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Update existing Lattice standards after a significant change — the update-mode counterpart to lattice-init. Scans .lattice/standards/, asks what changed, and routes each affected standard to its refiner's revise mode, recording a git-native change note. Use when the user says 'update refiners', 'refiners update', 'our standards changed', 'update our standards', 'the architecture changed, update the standards', 'we switched languages, update the standards', 'revise standards after a big change', or 're-run the refiners'.
日本語の概要は準備中です。原文の説明を表示しています。
Produce anime-style and stylized 2D animation with generative image and video tools as a craft discipline, not a filter. Use when a request asks for anime, manga-style, cel-shaded, sakuga, shonen/shojo/seinen/slice-of-life, mecha, or retro-90s-OVA animation; when planning shots, motion, and cutting rhythm to anime convention; when holding a character on-model and preventing style drift across shots or episodes; when choosing prompting vocabulary that actually controls anime look; when pairing voice, music, and impact SFX to stylized action; and when navigating the cultural, IP, and platform-policy sensitivities of AI anime (studio/artist style imitation, fan-art and IP boundaries, disclosure and monetization). This is provider-neutral; models are named only as illustrative options.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor brand mentions, sentiment, and reputation across Twitter, Reddit, news, and social platforms through SandBase. Use when asked for brand monitoring, reputation tracking, social listening, PR coverage analysis, or competitive brand intelligence.
日本語の概要は準備中です。原文の説明を表示しています。
Find and synthesize research papers, whitepapers, PDFs, technical reports, and academic sources with Firecrawl Research, using semantic paper search, related-paper expansion, and in-body verification over Firecrawl's paper index — largely biomedical and life-science literature from PubMed, bioRxiv, and medRxiv, plus arXiv preprints in CS, physics, and math. Use when the user wants a literature review, systematic review, survey of studies, paper summary, research landscape, or sourced synthesis from scholarly and industry publications, including clinical, drug, gene, disease, epidemiology, and public-health topics. Prefer this over a general web-research workflow whenever the evidence base is published papers rather than web pages.
日本語の概要は準備中です。原文の説明を表示しています。
Writes and rewrites the words on marketing pages: homepage, landing page, pricing, feature, product and about pages, including headlines, button text, section copy, title tag and meta description. Starts from the reader's own language and the proof the business can show, edits copy where it lives in the repository, and flags every claim that needs evidence. Use when someone says "write copy for this page", "rewrite our homepage", "this page sounds generic", "headline ideas", "better CTA", "landing page copy for this ad" or "pricing page wording". Email copy belongs to email-sequence, popups to popup-cro, and line-editing a finished draft to copy-editing.
日本語の概要は準備中です。原文の説明を表示しています。
World-class marketing expertise combining Seth Godin's permission marketing philosophy, Neil Patel's data-driven growth tactics, and the strategic frameworks from brands like Apple, Nike, and Dollar Shave Club. Marketing is the art and science of creating customers. Great marketing isn't about shouting louder - it's about being more relevant. The best marketers understand that attention is earned, not bought. They build systems that compound, create word-of-mouth, and turn customers into advocates. Marketing is the bridge between what you've built and the people who need it. Use when "marketing, campaign, go-to-market, gtm, launch, promotion, advertising, ads, acquisition, demand gen, lead gen, channel, funnel, conversion, cac, customer acquisition, reach, awareness, consideration, marketing, advertising, acquisition, campaigns, gtm, demand-generation, analytics, channels" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Angular is opinionated and comprehensive - it gives you everything: routing, forms, HTTP, dependency injection, testing. The learning curve is steep, but once you're in, you move fast. The structure it enforces is why enterprises love it. This skill covers Angular 17+, standalone components, signals, the new control flow syntax, and modern Angular patterns. Key insight: Angular's power is in its DI system and RxJS integration. Master those, and everything else follows. 2025 lesson: Standalone components are the future. NgModules aren't going away, but new projects should start standalone. Signals are Angular's answer to fine-grained reactivity - learn them. Use when "angular, angular component, angular service, angular routing, angular forms, rxjs, ngrx, angular signals, standalone component, angular ssr, angular, typescript, frontend, spa, enterprise, rxjs, signals, standalone" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Azure AI Content Understanding SDK for Python workflow skill. Use this skill when the user needs Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Influencer Discovery workflow skill. Use this skill when the user needs Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Influencer Discovery workflow skill. Use this skill when the user needs Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Android Jetpack Compose Expert workflow skill. Use this skill when the user needs Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
🧠 Andru.ia Niche Intelligence (Dominio Experto) workflow skill. Use this skill when the user needs Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
🔨 Andru.ia Skill-Smith (The Forge) workflow skill. Use this skill when the user needs Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa
日本語の概要は準備中です。原文の説明を表示しています。
B2B 大客户销售 (B2B 大客户销售 / 企业级复杂销售 (Enterprise B2B Sales / Complex Selling) — 面向企业客户的高价值、长周期、多干系人复杂销售的职业认知操作系统，从业者(AE/客户经理/SE 售前/销售负责人 VP Sales/CRO)、想入行者、以及服务这行(销售咨询/enablement/RevOps)的视角。覆盖: (a) 第一性张力 — 三大方法论流派之争: **买方主导的诊断式提问 (consultative/discovery-led: SPIN 提问 → 痛点 → 方案, 「像医生先诊断再开方」) ⇄ 卖方主导的教学式挑战 (Challenger: Teach-Tailor-Take control, 用商业洞见 reframe 客户认知, 「像老师挑战客户的既有想法」) ⇄ 资格审查纪律 (MEDDIC/MEDDPICC: 先严格 qualify/disqualify, 「no deal 好过 bad deal」)**; 三派不是非此即彼, 资深人混用, 但底层世界观分歧真实(问 vs 教 vs 筛); 更深层张力 — 「过程/方法论纪律 (process rigor: 预测准确、deal inspection、qualify) ⇄ 关系/信任 (relationship: champion 培养、高管关系、人情)」, 「卖结果/业务价值 (business outcome/ROI、卖给经济决策人) ⇄ 卖产品/功能 (feature selling)」, 「多线程触达买方委员会 (multithreading buying committee) ⇄ 单一 champion 依赖」; (b) 方法论正典 (最标准化、最易蒸出高质量+CLI 化) — MEDDIC/MEDDPICC (Metrics 量化指标/Economic buyer 经济决策人/Decision Criteria 决策标准/Decision Process 决策流程/Identify Pain 痛点/Champion 内部拥护者 + Paper process 签约流程/Competition 竞争), SPIN (Situation/Problem/Implication/Need-payoff 提问序列), Challenger (商业洞见 commercial insight + reframe + 建设性张力 constructive tension + Mobilizer 调动者), Solution Selling (痛点链 pain chain/愿景创建/buying vision), Sandler (前置合约 up-front contract/痛苦漏斗 pain funnel/潜艇七步), Command of the Message (Force Management: 业务价值框架/before-after/decision criteria), Gap Selling (Keenan: 现状 current state → 期望 future state → 差距 the gap/问题中心), Miller Heiman Strategic Selling (蓝表 blue sheet/buying influences: 经济/用户/技术买家 + coach), Value Selling, BANT (老式资格框架, 多被 MEDDIC 取代); (c) 行业结构与角色 — SDR/BDR (开发/约见) → AE/客户经理 (成交) → SE/售前/Solutions Engineer (技术验证/POC/demo) → CSM (客户成功/续约扩张) → Sales Manager/VP Sales/CRO; RevOps (收入运营), Sales Enablement (赋能); land and expand (先落地再扩张)、量化指标 quota/OTE(目标总收入)/配额达成率/pipeline coverage(管道覆盖率 ~3x 业内经验法则)/win rate(赢率)/sales velocity(销售速度)/ramp time(爬坡期)/ACV·ARR·NRR(年合同额/年经常性收入/净收入留存); (d) 销售周期 (the deal/opportunity lifecycle) — prospecting 开发 → discovery 需求挖掘 → qualification 资格审查(MEDDIC) → demo/technical validation/POC 技术验证 → business case/value 业务价值与 ROI → proposal 提案 → negotiation 谈判(procurement 采购/法务/security review) → close 成交 → onboarding/expansion 交付与扩张; 干系人: champion 拥护者 vs coach 线人 vs economic buyer 经济决策人 vs blocker 阻碍者; mutual action plan/close plan(双向行动计划/成交计划); (e) 产出物与节奏 — discovery call(需求电话)、demo、business case、proposal/SOW、MAP(mutual action plan)、forecast(预测: commit/best case/pipeline 类别)、pipeline review/deal review/QBR(季度业务回顾)/account plan(客户计划); (f) 职业/招聘/薪酬 — quota/OTE/comp plan(底薪+提成)/accelerator(加速器)/SPIFF/clawback、ramp、President's Club(顶尖销售俱乐部)、SDR→AE→管理 晋升路径、rep turnover(销售流失率高); (g) 争议/批判 — Challenger 是否过誉(CEB 原始数据被质疑、insight selling 批评)、MEDDIC 沦为填表剧场(box-checking theater, 填字段不真 qualify)、活动指标 vs 质量(spray-and-pray 群发/冷电话存废之争)、AI SDR/自动化淹没收件箱(2024-2025 AI BDR 泡沫 + 邮件送达率崩溃 backlash)、SDR 军团模式是否将死(Winning by Design/signal-based GTM 取代)、配额虚高与销售 burnout、季末打折促单、销售方法论的「宗教化」与培训-认证产业链、最大竞争对手其实是「no decision/维持现状」而非对手; (h) 流派/思想谱系 — 提问诊断派(Rackham SPIN/Bosworth&Eades Solution Selling/Keenan Gap Selling) vs 挑战教学派(Dixon&Adamson Challenger/Force Management Command of the Message) vs 资格纪律派(MEDDIC: Napoli&Dunkel 起源/John McMahon/MEDDICC Andy Whyte) vs 关系战略派(Miller Heiman Strategic/Large Account) vs SaaS 现代收入架构派(Aaron Ross Predictable Revenue/Mark Roberge Sales Acceleration Formula/Jacco van der Kooij Winning by Design bowtie/David Skok 指标) vs 开发-心态派(Jeb Blount Fanatical Prospecting/Sales EQ、Anthony Iannarino、Josh Braun) vs 谈判(Chris Voss Never Split the Difference 战术同理心)。不含: B2C/零售/电商导购销售、纯电话客服/客户支持、纯渠道/分销管理(channel 虽相关但聚焦直销复杂销售)、纯 marketing/需求生成(demand gen 虽上游但本 skill 聚焦销售执行)、纯 CSM 客户成功(虽相关但聚焦 new logo + expansion 的销售动作)。) Master OS — automated mastery of B2B 大客户销售 / 企业级复杂销售 (Enterprise B2B Sales / Complex Selling) — 面向企业客户的高价值、长周期、多干系人复杂销售的职业认知操作系统，从业者(AE/客户经理/SE 售前/销售负责人 VP Sales/CRO)、想入行者、以及服务这行(销售咨询/enablement/RevOps)的视角。覆盖: (a) 第一性张力 — 三大方法论流派之争: **买方主导的诊断式提问 (consultative/discovery-led: SPIN 提问 → 痛点 → 方案, 「像医生先诊断再开方」) ⇄ 卖方主导的教学式挑战 (Challenger: Teach-Tailor-Take control, 用商业洞见 reframe 客户认知, 「像老师挑战客户的既有想法」) ⇄
日本語の概要は準備中です。原文の説明を表示しています。
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live. One step stays a Console action by design and the skill hands it to you: granting the service account release access the first time. Use when uploading or promoting an Android build, wiring a Play service account and fastlane supply lanes, fixing per-versionCode changelogs, raising or halting a staged rollout, or answering what version and fraction production is really serving. NOT FOR: planning or building the app itself (use android-app-factory); live listing and keyword audits (use suede-aso); CI required checks (use suede-ci-gate); iOS release (a private Suede Labs companion, not in this pack: ios-app-store-release).
日本語の概要は準備中です。原文の説明を表示しています。
Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).
日本語の概要は準備中です。原文の説明を表示しています。
Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. NOT FOR: iOS work (private Suede Labs companion, not in this pack: ios-app-factory), a review-only pass on an existing app (use suede-code-review), or live Play listing and keyword audits on a shipped app (use suede-aso).
日本語の概要は準備中です。原文の説明を表示しています。
Find the papers that answer a research query in Firecrawl's research paper index — a corpus of paper abstracts whose largest share is biomedical and life-science literature (PubMed, bioRxiv, medRxiv), alongside arXiv preprints in CS, physics, and math — using semantic search, semantic and structural expansion, and in-body verification. Use this skill for literature-finding and paper-retrieval tasks of any kind, including clinical, biomedical, drug, gene, disease, and other life-science questions, whether the answer is a single paper or a full multi-paper set. The index is reached only through the `firecrawl_research_*` MCP tools or the `firecrawl research` CLI subcommands. Calling `firecrawl_search` with its `categories` option set to `["research"]` is a different feature — it filters ordinary web search to research-affiliated websites (the list includes PubMed, bioRxiv, medRxiv, arXiv, and publisher sites) and returns page results from them, without querying the paper records in this index.
日本語の概要は準備中です。原文の説明を表示しています。
Find and synthesize research papers, whitepapers, PDFs, technical reports, and academic sources with Firecrawl Research, using semantic paper search, related-paper expansion, and in-body verification over Firecrawl's paper index — largely biomedical and life-science literature from PubMed, bioRxiv, and medRxiv, plus arXiv preprints in CS, physics, and math. Use when the user wants a literature review, systematic review, survey of studies, paper summary, research landscape, or sourced synthesis from scholarly and industry publications, including clinical, drug, gene, disease, epidemiology, and public-health topics. Prefer this over a general web-research workflow whenever the evidence base is published papers rather than web pages.
日本語の概要は準備中です。原文の説明を表示しています。