「bloc」の検索結果

Google and Meta paid media account structure evaluation. Audits campaign/ad set architecture against conversion volume minimums, budget thresholds, and targeting overlap. Identifies over-segmentation, under-segmentation, budget fragmentation, and structural anti-patterns blocking algorithmic learning. Provides consolidation roadmaps with migration plans. Use when inheriting accounts, quarterly health checks, or before scaling budgets.

日本語の概要は準備中です。原文の説明を表示しています。

Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when "file upload, S3, R2, presigned URL, multipart, image upload, cloud storage, file-upload, s3, r2, storage, presigned, images" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert knowledge for environment art in games - modular design, visual hierarchy, color scripting, environmental storytelling, optimization, and world-building. From blockout to final art pass, creating immersive, performant, and readable spaces. Use when "environment art, level art, world art, modular kit, kit-bashing, set dressing, prop placement, biome design, visual hierarchy, color script, hero prop, trim sheet, environment composition, skybox, atmosphere, environment, level-art, world-building, modular, kit-bashing, set-dressing, visual-design, game-art, composition, optimization" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Formal Design of Experiments (DOE) methodology for maximizing information from experiments while minimizing resources. Covers factorial designs, blocking, randomization, and optimal design strategies. Use when ", " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in Claude Code hooks - user-defined shell commands that execute at specific points in Claude Code's lifecycle. Provides guaranteed automation that doesn't rely on the LLM "remembering" to do something. Essential for enterprise workflows, code quality enforcement, and deterministic behavior in agentic coding. Use when "claude code hooks, automate claude, block tool use, pre tool use, post tool use, session start hook, claude lifecycle, claude-code, automation, hooks, lifecycle, cli, workflow, devtools" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building DeFi protocols, implementing AMMs, yield farming strategies, or integrating with Ethereum/L2s - covers smart contract patterns, liquidity pools, and security considerationsUse when ", " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Azure AI Content Safety REST SDK for TypeScript workflow skill. Use this skill when the user needs Analyze text and images for harmful content with customizable blocklists and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Azure AI Content Safety REST SDK for TypeScript workflow skill. Use this skill when the user needs Analyze text and images for harmful content with customizable blocklists and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Async Python Patterns workflow skill. Use this skill when the user needs Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Async Python Patterns workflow skill. Use this skill when the user needs Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Async Python Patterns workflow skill. Use this skill when the user needs Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

加密链上交易 (加密 / 链上交易 (Crypto & On-chain Trading) — 以加密资产为标的、强调链上活动的主动交易认知操作系统：从「看叙事/选赛道 → 找标的 → 链上尽调与风控 → 选场所(DEX/CEX/链上合约) → 建仓与仓位管理 → 监控链上流向与情绪 → 退出与复盘」的完整决策链。覆盖 (a) 第一性张力 — **链上 on-chain (DEX 现货/AMM、钱包追踪 wallet tracking、资金流向 flow、MEV、memecoin、链上衍生品 Hyperliquid/GMX、自托管 self-custody, 'not your keys not your coins') ⇄ 链下 CEX (中心化交易所现货/合约 Binance/OKX/Bybit、订单簿、托管、出入金法币)**; **合约/杠杆/衍生品 (perps 永续、资金费率 funding、清算 liquidation、爆仓、做多做空、高频/择时) ⇄ 现货/价值/长持 (spot、HODL、定投 DCA、基本面/估值、'time in market > timing the market')**; **价值/基本面派 (协议收入、TVL、代币经济学 tokenomics、真实使用、估值模型) ⇄ meme/叙事/情绪派 (memecoin、narrative rotation 叙事轮动、attention is the asset、纯博弈/PvP、Ponzinomics)**; **链上数据/量化/客观 (on-chain analytics, Nansen/Arkham/Dune、聪明钱 smart money、链上指标、系统化/机械化) ⇄ 直觉/盘感/叙事阅读 (narrative、KOL alpha、社群情绪、tape reading)**; **自托管/去中心化/抗审查 (DeFi、自托管钱包、抗审查、'be your own bank') ⇄ 便利/合规/中心化 (CEX、合规出入金、KYC、托管、ETF)**; **主动交易/择时/高换手 (trading、波段、合约、撸毛/空投 airdrop farming、套利 arbitrage) ⇄ 被动配置/低换手 (配置 BTC/ETH、ETF、长期叙事 beta)**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量 + CLI 化) — 通用链: 叙事/赛道判断 (宏观周期/减半/流动性/板块轮动) → 标的发现 (链上扫链/聪明钱跟单/新币/叙事映射) → 尽调 due diligence (代币经济学/解锁 unlock/团队/合约审计/honeypot 检测/流动性与持仓分布) → 风控前置 (仓位 sizing/最大回撤/止损/相关性) → 场所与执行 (CEX vs DEX、滑点/MEV/gas、限价 vs 市价、TWAP) → 持仓监控 (链上流向/巨鲸/资金费率/解锁日历/情绪指标) → 退出与复盘 (止盈分批/再平衡/记录交易日志); 子流派 SOP: 链上 degen 打新与 memecoin 流程、合约交易者的资金费率与清算地图、空投/撸毛 farming、套利与 MEV、被动配置与定投; (c) 工具栈 — 链上分析 (Nansen 聪明钱/Arkham 实体标注/Dune 自建仪表盘/Dexscreener & DEX Screener 新币/GMGN & Photon & BullX memecoin 终端/Etherscan & Solscan 区块浏览器/DeBank 钱包总览/Token Terminal 协议基本面/DefiLlama TVL/Glassnode & CryptoQuant 链上指标)、交易场所 (CEX: Binance/OKX/Bybit/Coinbase; 链上现货 DEX: Uniswap/Jupiter/Raydium/Aerodrome; 链上衍生品: Hyperliquid/GMX/dYdX)、钱包与安全 (MetaMask/Rabby/Phantom 热钱包、Ledger/Trezor 硬件冷钱包、Revoke.cash 授权管理、honeypot/合约扫描)、行情与图表 (TradingView、CoinGecko/CoinMarketCap)、信息与聚合 (Twitter/X、Telegram、DeFiLlama、RootData/ICO 日历、解锁日历 Token Unlocks)、自动化 (交易机器人、链上 bot/sniper、Telegram trading bot); (d) 知识正典 — 注意加密交易 canon 偏少且新: 通用交易/风控经典 (Edwin Lefèvre 'Reminiscences of a Stock Operator'、Van Tharp 'Trade Your Way to Financial Freedom' 仓位管理、Mark Douglas 'Trading in the Zone' 交易心理、Michael Mauboussin、Nassim Taleb 'Fooled by Randomness/Antifragile')、加密原生 (Bitcoin whitepaper 中本聪、'The Bitcoin Standard' Saifedean、Vitalik 博客与 Ethereum whitepaper、'DeFi and the Future of Finance'、Lyn Alden 宏观、a16z crypto 文章、Messari/Delphi/Bankless 研报)、链上分析方法 (Glassnode/CryptoQuant 教程、Nansen/Arkham/Dune 文档、Dune Analytics SQL)、交易方法论散见于 podcast/Substack/Twitter thread 而非书; (e) figures/流派 — 价值/基本面派 (Vitalik Buterin 以太坊、Hasu/Su Zhu(争议)、Arthur Hayes BitMEX 创始人/宏观+衍生品、Raoul Pal、Lyn Alden 宏观、Cobie/Jordan Fish UpOnly podcast、DeFi 研究 Bankless Ryan Adams/David Hoffman); 链上分析派 (Nansen Alex Svanevik、Arkham、Adam Cochran、Ansem(blknoiz06) 链上交易、Murad memecoin supercycle、链上侦探 ZachXBT 反诈); 合约/衍生品派 (Arthur Hayes、GCR(GiganticRebirth) 传奇合约、Pentoshi、CryptoCred 技术分析、Tyler Durden); meme/叙事派 (Ansem、Murad、Cobie、各 Solana memecoin KOL); 宏观/周期派 (Raoul Pal、Lyn Alden、PlanB stock-to-flow(争议)、Benjamin Cowen 数据/周期); 量化/系统化 (各匿名量化、Hyperliquid 生态); 中文圈 (链上分析/合约 KOL、币圈大 V、播客如 '无人之境'/'Web3 佛学院'、研究机构如 Foresight/PANews/律动 BlockBeats); 反诈/安全 (ZachXBT、SlowMist 慢雾、go+ 安全); (f) 行业话术/黑话 — 现货 spot / 合约 perps 永续 / 杠杆 leverage / 多空 long-short / 爆仓 liquidation 清算 / 资金费率 funding rate / 开多开空 / 止损 SL 止盈 TP / 仓位 position sizing / 满仓梭哈 ape in / 梭 / FOMO / FUD / 钻石手 diamond hands / 纸手 paper hands / 韭菜 / 镰刀 / 庄 / 出货 / 拉盘砸盘 / 插针 wick / 针 / 上车下车 / 埋伏 / 潜伏 / 链上 on-chain / 钱包 wallet / 地址 / 聪明钱 smart money / 巨鲸 whale / 跟单 copy-trade / 老鼠仓 / 貔貅盘 honeypot / 貔貅 / rug 跑路 rug-pull / 归零 / 土狗 (memecoin/小币) / 金狗 (暴涨百倍) / meme 币 / 叙事 narrative / 赛道 / 板块轮动 / 撸毛 撸空投 airdrop / 女巫 sybil / 交互 / 解锁 unlock / 砸盘解锁 / 代币经济学 tomomics / TVL / APY APR / 无常损失 IL / 滑点 slippage / MEV / 三明治 sandwich / gas / 抢跑 frontrun / 貔貅检测 / 授权 approve / 撤销授权 revoke / 私钥 助记词 seed phrase / 冷钱包 热钱包 / 自托管 / 减半 halving / 牛熊 / 山寨季 altseason / 比特币市占率 BTC.D / 山寨 alt / 主流币 / DeFi 暑期 / GM / WAGMI / NGMI / 归零归零 / PvP / Ponzi 庞氏; (g) 争议/批

日本語の概要は準備中です。原文の説明を表示しています。

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 客户认知, 「像老师挑战客户的既有想法」) ⇄

日本語の概要は準備中です。原文の説明を表示しています。

健身私教 — 为客户设计、指导和推进个性化训练方案的专业工艺, 有别于团课教练、物理治疗师或运动队教练: (a) 训练方案设计与周期化 (线性 / 波动 / 板块周期化 Bompa & Haff; NSCA《力量训练与体能训练精要》行业圣经; Schoenfeld 肌肥大机制; Helms/Valdez/Morgan 肌肉与力量金字塔; 共轭训练法 Simmons/Westside; Starting Strength 线性渐进 Rippetoe; Renaissance Periodization 训练量地标 Israetel); (b) 动作评估与筛查 (FMS 功能性动作筛查 Gray Cook; NASM CEx 纠正性训练连续体 抑制-拉伸-激活-整合; 关节逐级方法 Cook/Boyle; 姿势与代偿模式识别; PAR-Q+ 与 ACSM 运动前筛查指南); (c) 教学与指令 (外部 vs 内部注意焦点 Wulf; 差异化学习 Schöllhorn; 约束导向方法 Davids/Renshaw; RIR/RPE 自动调节 Zourdos/Helms; 动机访谈在健身中的应用 Rollnick/Miller); (d) 营养指导的执业边界 (宏量营养素周期化; Precision Nutrition / ISSN 立场声明的循证建议; 边界: 私教提供一般性指导, 医学营养治疗需 RD/RDN 资质; 能量可用性与 RED-S Mountjoy IOC 共识); (e) 商业与客户管理 (客户留存与方案依从; 咨询与销售伦理; 线上教练平台与规模化 Goodman PTDC; 方案交付工具 TrueCoach/Trainerize/TrainHeroic; 课时定价模型; 独立教练 vs 健身房雇员); (f) 专项方向 (运动表现 CSCS; 纠正性训练 CES; 老年健身 SFN; 产前产后; 青少年 YSCA; 适应性 / 无障碍健身; 健美 / 形体; 力量举; 耐力运动 S&C)。诚实处理: 兄弟科学 vs 循证之争, 补剂行业利益冲突, 合成代谢激素使用现状 (诚实但不推广: 匿名调查约 30% 有经验男性健身者使用过 — 业内估, Kanayama/Pope/Hudson 记录健康风险, WADA 禁用清单用于竞技语境), 体型焦虑与进食障碍风险 (男性私教肌肉变形症, 正食症倾向, NEDA 负责任语言指南), 健身房掠夺性销售 (高压推销、误导性对比照、长约锁定), 执业边界违规 (私教诊断伤病或超范围开饮食处方), 线上教练认证造假 (周末速成、未经认可的认证)。不含: 物理治疗 / 康复治疗 (持照医疗职业), 不含: 团课教练 (Les Mills/Zumba/CrossFit 分馆教练 — 相邻但不同), 不含: 精英竞技运动教练 (团队项目周期化, 不同职业路径), 不含: 营养作为主业 (临床营养学需单独资质)。 (Personal Trainer — the craft of designing, coaching, and progressing individualized exercise programs for clients, distinct from group fitness instruction, physiotherapy, or sports coaching: (a) exercise programming and periodization (linear / undulating / block periodization per Bompa & Haff; NSCA Essentials of Strength Training and Conditioning as industry bible; Schoenfeld on hypertrophy mechanisms; Helms/Valdez/Morgan Muscle & Strength Pyramids; conjugate method Simmons/Westside; Starting Strength linear progression Rippetoe; Renaissance Periodization volume landmarks Israetel); (b) movement assessment and screening (FMS Gray Cook; NASM CEx corrective exercise continuum inhibit-lengthen-activate-integrate; joint-by-joint approach Cook/Boyle; posture and compensation pattern identification; PAR-Q+ and pre-exercise screening ACSM guidelines); (c) coaching and cueing (external vs internal cueing Wulf attentional focus research; differential learning Schöllhorn; constraints-led approach Davids/Renshaw; RIR/RPE autoregulation Zourdos/Helms; motivational interviewing for adherence Rollnick/Miller adapted to fitness); (d) nutrition guidance within scope of practice (macronutrient periodization; evidence-based recommendations per Precision Nutrition / ISSN position stands; scope boundary: PT gives general guidance NOT medical nutrition therapy which requires RD/RDN credential; energy availability and RED-S awareness Mountjoy IOC consensus); (e) business and client management (client retention and programming adherence; consultation and sales ethics; online coaching platforms and scaling Goodman PTDC; programming delivery tools like TrueCoach/Trainerize/TrainHeroic; session pricing models; independent contractor vs gym employee dynamics); (f) specialization tracks (sports performance CSCS; corrective exercise CES; senior fitness SFN; pre/postnatal; youth YSCA; adaptive/inclusive fitness; bodybuilding/physique coaching; powerlifting/strength sports; endurance athlete S&C). Evidence-based practice as the core ethos: Schoenfeld/Krieger meta-analyses on volume-response, Helms systematic reviews on protein/resistance training, Brad Schoenfeld's MASS journal bridging research to practice, Menno Henselmans and Eric Helms as practitioner-researchers, Greg Nuckols Stronger By Science as translation layer. Chinese fitness industry context: rapid growth of personal training in commercial gyms (Keep/Lefit/Megafit chains), NSCA-CPT and ACE-CPT as dominant certifications alongside local CSFA (China Sport and Fitness Association) credential, '体适能' (physical fitness) as formal term, online coaching boom post-COVID, PT business models in tier 1-3 cities diverge sharply. Honest treatment of: bro science vs evidence-based d

日本語の概要は準備中です。原文の説明を表示しています。

Triage the deferred-work ledger for the bmad-loop orchestrator: verify every selected open entry against the actual codebase and return a machine-readable partition (bundles, already-resolved, blocked, skip, human decisions). Also migrates legacy pre-DW-format ledgers when invoked with --migrate. Automation-only — invoked by bmad-loop sweep runs, not by humans.

日本語の概要は準備中です。原文の説明を表示しています。

Runs a multi-step procedure as a Python DAG, so ordering, branching and retries are enforced by the runner rather than described in prose a model can generate past. Use for "run these steps in order and retry the flaky one until the check passes", "build a pipeline that fetches, validates, then skips the upload when nothing changed", "make sure these steps cannot be skipped", "resume from where it broke instead of redoing the expensive early stages", "run these independent calls at once and merge the results", or any procedure of 3+ steps with branches, input contracts, or side effects that must not block the critical path. Primitives are depends_on, when=, validate=, retry_until=, detached= and journal_path=. Not for a single sequential call, for steps needing reasoning between them that no predicate captures, or for async and distributed work. To audit whether one verification check can actually go red, use gating. To fan work out across many subagents, use a dynamic workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Build and audit deterministic verification gates — a check that blocks a pipeline and can be shown to go red. Use when writing a calibration gate, CI check, validation script or pre-publication check for a numeric or empirical result; when a plausible-but-wrong value would survive review; when asking whether an existing test, linter rule or check could actually fail; and when a suite passes first try, passes suspiciously often, or was written by whatever produced the thing it checks. Triggers on "can this check fail", "known-bad", "negative control", "calibration gate", "sanity check my results", "is this test actually testing anything".

日本語の概要は準備中です。原文の説明を表示しています。

Close a GitHub issue with a synthesis comment as a flowing graph — validate the synthesis, post the closing comment, close, then run a pluggable callback (e.g. memory store) detached. Use when closing an issue should also capture the LEARNING (not just the diff log) and when the post-close work shouldn't block the close ack.

日本語の概要は準備中です。原文の説明を表示しています。

Debug the AWF firewall by inspecting Docker containers (awf-squid, awf-agent), analyzing Squid access logs, checking iptables rules, and troubleshooting blocked domains or network issues.

日本語の概要は準備中です。原文の説明を表示しています。

Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use this skill whenever the user says 'capture this', 'brain dump', 'let me dump some ideas', 'I've got a bunch of thoughts', 'here's everything on my mind', 'idea dump', 'let me get this out of my head', 'I need to organize my thoughts', 'here's what I'm thinking', or any variation where someone is unloading a messy stream of ideas, tasks, thoughts, and plans wanting them turned into something coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas — even without the exact phrase — the intent is the same. Fast-to-action by design: no upfront intake. Output is four sections (Projects/Ideas, Tasks, Connections, How I Can Help) ending with a directive question. Asks at most one mid-organization clarifying question when a single item is genuinely ambiguous between task and project.

日本語の概要は準備中です。原文の説明を表示しています。

Draft a reply or a value-add quote tweet for a specific X (Twitter) tweet from its URL. Use to reply in a thread, answer a creator, or quote-tweet with added value. Parses the tweet URL, reads pasted context, decides reply vs quote tweet, and drafts 1-3 variants in your voice. X has no LinkedIn-style 2-level thread flattening, so a reply is just a tweet. Publora has no reply endpoint, so the draft is returned as a copy-paste block to post yourself. Not for top-level posts (use x-post-writer).

日本語の概要は準備中です。原文の説明を表示しています。

Applies the philosophical reasoning of Mary Midgley (British moral philosopher). Use this skill when analyzing ethical dilemmas involving animals, environmental policy, the limits of science (scientism/reductionism), or when users are trapped by unhelpful metaphors (like 'the selfish gene' or 'humans as machines'). Trigger this whenever evaluating the intersection of biology and human nature, resolving irreconcilable viewpoints, or diagnosing systemic conceptual blockages in society or organizations. Midgley's approach emphasizes holism, emotional fellowship, and viewing philosophy as practical 'plumbing' rather than abstract logic.

日本語の概要は準備中です。原文の説明を表示しています。

Suede Labs skill that lints a local music or media release folder and scores it for release readiness: missing files, weak or malformed metadata, artwork and stem problems, split gaps, rights blockers, and platform-delivery issues, produced by a bundled offline script as a scored markdown and JSON report. Use when a creator has one or more release folders of tracks, artwork, and stems and wants to know what is missing before distributing, delivering, or handing it off; when metadata quality or a delivery rejection is the question; or when a release-readiness score is asked for. Reports what is present, missing, or unknown; never upgrades unknown to confirmed and never means legal clearance. NOT FOR: organizing the evidence behind a rights or split gap the report surfaces (use suede-rights-audit); building the transfer package (use suede-rights-passport); a sync one-sheet (use suede-sync-packaging).

日本語の概要は準備中です。原文の説明を表示しています。

Suede AI CI and branch-protection wiring for any repo and any stack: path-aware jobs, a single aggregator required check that cannot deadlock, lockfile hygiene, runtime pinning from the repo, and the exact branch-protection settings. Use when asked to set up CI, protect main, make CI block a bad merge, fix a required check that hangs pending forever, or repair duplicate or misfiring pipelines. Detects the repo's real apps, package managers, and runtime versions first; emits workflow files and settings, never pushes or flips protection itself. NOT FOR: reviewing or grading the change the gate is failing on (use suede-code); designing the AI eval cases to wire in (use suede-ai-eval); branch and worktree hygiene (a private Suede Labs companion, not in this pack).

日本語の概要は準備中です。原文の説明を表示しています。