3,232 件 ・ 関連度順
概要と使いどころ
Read the branch diff in dynamic-neural-field-composer and print a PR title and description in chat, filling the repo's pull request template. Use when asked to write, draft or suggest a PR title/description, or "what should the PR say".
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "implement a DiD regression", "run a staggered difference-in-differences", "set up an event study", "implement IV / 2SLS", "run a regression discontinuity design", "build synthetic control", "do propensity score matching", "test parallel trends", "run Honest DiD", "wild cluster bootstrap", "Callaway-Sant'Anna", "Sun-Abraham", "Bacon decomposition", "double machine learning", "debiased machine learning", "DML / DoubleML", "cross-fitting", "causal forest", "heterogeneous treatment effects", "ATE with ML controls", "which causal design fits my data", or needs causal-inference code, diagnostics, or identification writing in Python (StatsPAI), R, or Stata. Based on Scott Cunningham's Causal Inference: The Mixtape, with runnable validated templates, ML-based causal inference patterns, and Journal of Finance applications.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementation and tests are complete and a human must choose how local branch work should be integrated or preserved
日本語の概要は準備中です。原文の説明を表示しています。
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
日本語の概要は準備中です。原文の説明を表示しています。
Map the most influential Reddit venues for a brand's AI visibility using Xpoz. Finds which subreddits and threads AI engines actually cite when answering buyer questions, where those questions get asked, and which live threads are worth answering. Use when asked to "get cited by AI through Reddit", "which subreddits matter for my brand", "Reddit influence map", "where should we engage on Reddit", or "why does ChatGPT cite Reddit for my category".
日本語の概要は準備中です。原文の説明を表示しています。
塔罗牌占星：把「抽三张塔罗牌」与「西方占星本命盘」合为一次解读。 用户带着一个具体问题来 → 抽三张牌（可复现的 seed）→ 若愿意提供生日，则用脚本 确定性地排出星座与星盘 → 用黄金黎明的塔罗↔占星对应把两者接起来（牌落在黄道哪一旬， 你的哪颗行星正站在那里）→ 给出一张交叉对照表、对所问之事的审慎取向与可执行建议。 塔罗层：牌阵位置语义、牌与牌的组合叙事、元素尊贵、正逆位、直觉对话、治疗性解读。 占星层：本命盘、相位与宫位、必然尊贵、行运盘推运、比较盘/组合盘（合盘）、太阳弧推运。 当用户说：塔罗、塔罗牌、抽牌、抽三张牌、占卜、算一卦（西洋）、牌阵、正逆位、 星盘、本命盘、星座、上升星座、月亮星座、占星、行运、流年、合盘、比较盘、 太阳弧、推运、我该不该……、这段关系会怎样、我适不适合换工作 时使用。 English triggers: "tarot", "tarot reading", "draw three cards", "what do the cards say", "spread", "reversed card", "natal chart", "birth chart", "astrology", "rising sign", "transits", "synastry", "composite chart", "solar arc", "progressions", "should I take this job", "what does my chart say". 内置离线脚本：抽牌洗牌（可复现 seed）、本命盘（行星/四轴/宫位/相位/元素统计）、 必然尊贵、牌↔盘共鸣、元素数字统计、行运盘、比较盘+组合盘、太阳弧+次限推运。 边界：要**周公解梦**请用 `zhougong-dream-interpretation`；要**四柱八字**请用 `bazi`； 要**中式黄历择日/测吉凶**请用 `zhanshi-jixiong`。本技能只做西洋塔罗与西洋占星。 即使用户只是随口说「帮我抽张牌看看」「我最近水逆吗」，也应主动使用本技能。
日本語の概要は準備中です。原文の説明を表示しています。
占事吉凶 · 测吉凶：针对**某一件具体事、某一天、某一刻**的吉凶研判与择吉建议。 运用「黄历择日 + 四柱命理本命喜忌 + 阴阳五行天时地利 + 天人感应/梅花心易」四层独立推演， 再交叉汇聚成【吉 / 平·宜谨慎 / 凶·宜改期】的整体倾向与可执行建议。 当用户问：测吉凶、占吉凶、这事能不能做、今天适不适合出门/旅行/搬家/开业/签约/求医、 出行吉凶、看日子、择日、挑个好日子、黄历、老黄历、今天宜不宜、宜忌、冲煞、起一卦、 算算这件事顺不顺、"临出发前忽然心悸/心慌，是不是预兆"、"我有种不好的预感" 时使用。 English triggers: "is today auspicious", "is it a good day to travel/move/sign", "should I go today", "pick an auspicious day", "Chinese almanac / huangli", "divination for a decision", "I have a bad feeling about going out today". 内置离线脚本：公历→农历+完整四柱+十神（bazi.py）、黄历宜忌/建除/值神/廿八宿/彭祖百忌/ 冲煞/吉神凶煞/逐时辰吉凶+梅花时间起卦（almanac.py）、经纬度定位+当天当地天气（geoweather.py）。 边界：要**批一生八字/大运流年**请用 `bazi` 技能；要**解梦**请用 `zhougong-dream-interpretation`。 即使用户只是随口问「今天出门好不好」「这事顺不顺」，也应主动使用本技能。
日本語の概要は準備中です。原文の説明を表示しています。
Use when recording, tallying, or triaging stochastic review findings — the append-only JSONL ledger where Tier 2 (advisory, unevidenced) reviewer output goes instead of blocking language. Triggers on "log this finding", "ledger add", "tally the findings", "triage findings", "is this finding recurring", "retire this noise", or whenever a reviewer produces an unevidenced concern that should be measured for recurrence rather than chased. For the review itself see code-review-and-quality or skill-library-review; for verifying formal claims with deterministic evidence see adversarial-claims-reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit approval. Use on "QA scope for PROJ-123", "what should QA test", "write test scenarios for QA", "hand this ticket to QA", "prep the QA handoff", "gherkin scenarios for this ticket", or when a branch is ready for manual testing — even when the user only names the ticket or says "this branch".
日本語の概要は準備中です。原文の説明を表示しています。
Routes LLM requests to a local model first (Ollama, LM Studio, llamafile), validates the response quality, and escalates to cloud only when the local result fails. Tracks local vs escalated vs cloud outcomes in a persistent dashboard. Use when: (1) user asks to run a task with a local model first, (2) user wants to reduce cloud API costs or keep requests private, (3) user wants post-outcome quality validation before committing to a local result, (4) user asks to see token savings or the routing dashboard, (5) any request where local-vs-cloud routing should be decided automatically with a quality gate. Supports Ollama, LM Studio, and llamafile as local providers.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks for body doubling, ADHD focus sessions, accountability while working, help getting started on a task, pomodoro-style work sessions, or says things like 'I can't focus', 'I'm stuck', 'help me start', 'I need accountability', 'body double with me', 'I keep procrastinating', 'I can't get started', or 'focus session'. Provides punk-style ADHD body doubling with micro-step protocols, frequent check-ins, dopamine resets, and session history tracking. Part of the ADHD-founder.com ecosystem.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when interacting with Apple Calendar on macOS. Use it for listing calendars, viewing events, creating/updating/deleting calendar events, and checking availability/free-busy times. Triggers on requests like "check my calendar", "schedule a meeting", "what's on my schedule", "am I free tomorrow", or any calendar-related operations.
日本語の概要は準備中です。原文の説明を表示しています。
This is the MistEye security gate skill. It is triggered by pre-installation risk checks (including Skill/MCP dependency manifests), pre-access security checks for domains or URLs, IoC malicious detection, and supply-chain risk blocking, especially for common requests such as "take a look at this address/website." It must use `https://app-api.misteye.io/functions/v1/detect`; in dependency and external-link scenarios it has the highest priority. If the API returns `status="malicious"` or any `matches`, the action must be blocked and explicitly reported as "blocked". Only after the first installation is complete should the user be reminded that daily patrols can be enabled with OpenClaw or Hermes (default once per day).
日本語の概要は準備中です。原文の説明を表示しています。
Converts OpenAPI 3.0 JSON/YAML to TypeScript interfaces and type guards. This skill should be used when the user asks to generate types from OpenAPI, convert schema to TS, create API interfaces, or generate TypeScript types from an API specification.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).
日本語の概要は準備中です。原文の説明を表示しています。
Replace with description of the skill and when Claude should use it.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
日本語の概要は準備中です。原文の説明を表示しています。
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive logo & brand design strategist. Runs a strategy workshop, narrows a creative direction, lands a single centralized concept, then outputs a condensed branding table plus 10+ logo ideas with rationale. Use when the user wants to design a logo, develop a brand identity, write a logo brief, brainstorm logo concepts, or run brand strategy before sketching. Triggers include "design a logo", "logo ideas", "brand identity", "help me with my logo", "logo brief", "what should my logo be".
日本語の概要は準備中です。原文の説明を表示しています。
Agent Skill design knowledge base — mechanisms, philosophy, patterns, pitfalls. Use when: designing new skills, reviewing skill quality, or deciding whether something should be a skill.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate an incoming workflow upgrade — a skill, MCP server, subagent, library, external service, prompt, or pattern — through one disciplined pipeline before adopting it. Security is a blocking gate. Records every verdict so the same thing is never evaluated twice. Use when considering a new tool from a post, repo, or recommendation. Triggers — "vet this", "should we adopt", "is this safe to install", "evaluate this skill/MCP", "what do you think of this tool".
日本語の概要は準備中です。原文の説明を表示しています。