383 件 ・ 関連度順
概要と使いどころ
Explain trained machine learning models through feature attribution, local explanations, and behavior summaries. Use as an explicit/manual helper once a model already exists, not for training ownership, leakage auditing, or general ML strategy selection.
日本語の概要は準備中です。原文の説明を表示しています。
Compare current benchmark results against historical baselines to spot performance regressions. Use as an explicit/manual helper for build-to-build degradation review, not for broad optimization strategy or low-level profiling ownership.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate outliers, rare events, spikes, and suspicious records in datasets. Use as an explicit anomaly-analysis helper when you want concrete anomaly-detection workflow guidance, not generic data validation or end-to-end ML ownership.
日本語の概要は準備中です。原文の説明を表示しています。
Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See `samber/cc-skills-golang@golang-samber-ro` skill).
日本語の概要は準備中です。原文の説明を表示しています。
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "review this influencer content" or "check if this post meets brand guidelines"; runs the typed STAR pre-publish gate, scores Trust and Appeal on the deliverable, folds in the creator Suitability read, computes the profile-weighted SQS, checks the disclosure/claim/brand-safety and fraud/fake-engagement vetoes, and writes constructive revision feedback. Not for drafting the brief — use brief-generator; not for partnership terms — use contract-helper. 达人内容审核/发布前质检
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", or "negotiate partnership terms"; produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker — the shared outreach mechanics engine for creator, media/analyst, launch-partner, and social-selling / advocate-recruitment targets. Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations. 达人邀约建联/合作谈判话术
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "draft an influencer contract", "review these agreement terms", or "build a partnership template"; produces a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet. Not for outreach negotiation before a deal exists — use outreach-manager. 达人合同/合作协议条款审查
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "design an email A/B test", "set up a multivariate subject/CTA test", "run a send-time test", "build a hold-out group", or "is this email result statistically and practically material?"; produces a falsifiable hypothesis, one-variable-per-cell matrix, sample-size/MDE/duration/power plan, and an effect/uncertainty read from own ESP data. Applies only a precommitted owner-approved action rule; the helper never chooses a business action. Not for EQS/vetoes or writing the email. 邮件AB测试设计/多变量测试/发送时间测试/留出组/显著性判定
日本語の概要は準備中です。原文の説明を表示しています。
Build, validate, and run the claude-osint skills repo — check SKILL.md frontmatter, run the secret_scan.py and h1_reference.py helpers, run sync-skill-content.sh, run the smoke test. Use when asked to run, build, test, validate, or smoke-test claude-osint or its OSINT skills/scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Doctrine for designing and evolving any **SDK** Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface rejects the wrong contents and keeps the package testable in isolation. Default is "core, not customizable"; customization is the exception, defended by a deciding table. Use when authoring or evolving any such surface — `@grida/*` published packages, engine crates (gridaco/nothing `crates/*`) published or FFI-exported, intent/message vocabularies, any contract a second author will compile against. Internal-only helper packages are welcome to follow, not forced. Companion skill for two-sided contract work: $sdk-seam. Critique partners: $pedantic, $etiology. Related: $naming.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a benign transformation while omitting license metadata
日本語の概要は準備中です。原文の説明を表示しています。
Sync calendar events with an endpoint selected in configuration
日本語の概要は準備中です。原文の説明を表示しています。
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for the TRL (Transformer Reinforcement Learning) library codebase. Use proactively before reading or editing any file under `trl/` so you have the intended contracts and invariants in mind, not just what the current code says. Covers trainer hierarchy (SFT, DPO, GRPO, KTO), shared utility functions (selective_log_softmax, decode_and_strip_padding, padding helpers), configuration system, model wrappers, and how data flows through any TRL trainer.
日本語の概要は準備中です。原文の説明を表示しています。
Implements the core MCP Apps architectural pattern where a Tool declares _meta.ui.resourceUri referencing a registered Resource. Covers registerAppTool, registerAppResource, text fallback, structuredContent, and app-only helper tools.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses macOS system-level slowness, heat and fleet-wide timeouts: high load average, leaked per-session child processes (MCP servers, helpers), fork storms, busy loops. Use when the Mac feels slow or hot, fans spin up, or everything times out at once (电脑发烫/卡顿/负载高/全部超时). Not for single-app bugs, network slowness (use tunnel-doctor), launchd watchdog design (use macos-watchdog), or disk-full (use macos-cleaner).
日本語の概要は準備中です。原文の説明を表示しています。
Write a sincere condolence or sympathy message when someone has died or a friend is grieving — warm, personal, and free of the clichés that hurt more than help. Use when asked what to say when someone dies, write a sympathy/condolence message, my friend lost their [person], or I don't know what to say. Produces a heartfelt message tuned to your relationship and the situation, drawn from a specific memory or quality where possible, an honest acknowledgment (not toxic-positive platitudes), an offer of concrete support, and guidance on what to avoid saying.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 孩子这道题不会怎么教, 辅导作业总发火, 怎么给孩子讲应用题, 陪写作业, 作业太多写到很晚, or help a parent guide (not do) a child's homework in China. Produces, for the specific question, an age-appropriate way to explain it with guiding questions in order, a hint ladder that stops before the answer, a similar practice item, what to do if the child is stuck or upset, and a homework routine, written for the parent in Chinese; it never hands over a finished answer for the child to copy.
日本語の概要は準備中です。原文の説明を表示しています。
Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and I need to split caregiving, organize care for a sick family member, or set up a care schedule. Produces the care map of needs and coverage, the rotation schedule with escalation rules, the binder outline, and the family meeting agenda.
日本語の概要は準備中です。原文の説明を表示しています。
Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.
日本語の概要は準備中です。原文の説明を表示しています。
Draft the hard personal message you keep putting off — chasing money a friend owes, backing out of plans, checking in after a fight, following up on an unanswered text. Use when asked to help send an awkward text, how to say something uncomfortable to a friend, word a difficult personal message, or bring up something touchy. Produces a couple of calibrated options, the one line to open with, and the send/wait/call judgement call — warm, honest, and not a doormat.
日本語の概要は準備中です。原文の説明を表示しています。
Write and edit project docs (README/markdown) as a glossary of principles, not a mirror of the code. Use when creating or revising a README; when a doc enumerates exact scenes, scenarios, helpers, class ids, file lists, or command/flag matrices the code already holds; when trimming narrative or changelog out of a doc; or when deduplicating overlapping docs and wiring a root doc to its sub-docs.
日本語の概要は準備中です。原文の説明を表示しています。