7,943 件 ・ 関連度順
概要と使いどころ
Digital forensics techniques for detecting device compromise, analyzing malware indicators, and investigating targeted surveillance. Based on methodologies from Citizen Lab's Pegasus Project and Predator investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Clojure scripting without JVM startup.
日本語の概要は準備中です。原文の説明を表示しています。
Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for large-scale datasets.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and maintain Hierarchical Agent Memory (HAM) for Codex using scoped local memory files. Trigger on "go ham", "set up HAM", "ham commands", "ham help", "ham route", "ham remove", "ham update", "ham status", "ham benchmark", "ham baseline start", "ham baseline stop", "ham metrics clear", "HAM savings", "HAM stats", "HAM dashboard", "HAM sandwich", "HAM insights", "HAM carbon", or "HAM audit".
日本語の概要は準備中です。原文の説明を表示しています。
Set up Hierarchical Agent Memory (HAM) — scoped CLAUDE.md files per directory that reduce token spend. Trigger on "go ham", "set up HAM", "ham commands", "ham help", "ham route", "ham remove", "ham update", "ham status", "ham benchmark", "ham baseline start", "ham baseline stop", "ham metrics clear", "HAM savings", "HAM stats", "HAM dashboard", "HAM sandwich", "HAM insights", "HAM carbon", or "ham sync".
日本語の概要は準備中です。原文の説明を表示しています。
账号被限流/异常/担心操作触发风控/需要恢复时用：先自检from:@用户名搜不到即限流→区分临时标签(等24h不动账号)与正式标签(写申诉邮件+48h不操作)→复盘触发原因预防复发。Trigger："推文搜不到了""被限流了""账号异常""触发风控""临时标签""怎么申诉""shadowbanned""account suspended""appeal suspension""tweets not showing up"。不适用：正常发内容没出问题(→内容创作skill)、新号开业装修养号(→x-account-setup)、没粉丝怎么起量(→x-cold-start-playbook)。
日本語の概要は準備中です。原文の説明を表示しています。
规划变现路径/判断够不够格开创作者收益/决定卖什么产品时使用。三层金字塔定位：底层流量型(商单+广告分成,需500蓝V+3月5M曝光)、中层产品型(课程/付费专栏/带货)、顶层服务型(咨询/高端社群,利润率>80%)。IP路线可叠三层,泛流量卡底层。Trigger："怎么变现""够不够格开收益""卖什么产品""monetize""creator revenue""what to sell"。不适用：没粉丝的冷启动(→x-cold-start-playbook)、选IP还是泛流量(→x-positioning-tradeoff)、开蓝V/装修(→x-account-setup)。
日本語の概要は準備中です。原文の説明を表示しています。
Use for CRM audits, duplicate detection, missing or stale fields, job changes, domain checks, acquisitions, parent-child relationships, repair plans, prevention, monitoring, and evaluation. Supports HubSpot, Salesforce, Attio, and mapped exports. Start with read-only analysis. Skip outreach writing, CRM interface design, and unrelated analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Run a quick Deepline demo with a maintained Play.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when a story has been captured but content direction is unresolved - the spark describes WHAT to build structurally but not WHAT goes in it. Reads the story spark, splits it into Resolved (structurally clear) vs. Assumed (would have to guess) content dimensions, and surfaces each assumption for the human to confirm, correct, or expand. Also classifies implementation risk tags (has-variants, has-data-pipeline, has-animation, has-touch-targets, diverges-from-existing) so plan-chunks translates them into acceptance criteria that name the implementation mechanism. Captures answers into
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when validate-chunk reports errors or failures, when the user asks to "fix these errors", "resolve validation issues", "refine this chunk", or when specific build, lint, or type errors need surgical fixes. Makes precise, targeted edits to resolve specific validation issues without over-engineering.
日本語の概要は準備中です。原文の説明を表示しています。
A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.
日本語の概要は準備中です。原文の説明を表示しています。
Assess review findings against the target's governing contract, evidence, and consequence without imposing a lens-specific verdict, schema, or gate. Use when classifying a candidate concern in a code or change review.
日本語の概要は準備中です。原文の説明を表示しています。
Start-of-session situational report for a research or code repository. Reads the handoff, log, or status files the project actually keeps, checks live git state, and reports the objective, verified baseline, open tasks, blockers, and next actions, flagging where the documents and the repository disagree. Use when resuming work after time away or before changing anything. Its end-of-session twin is finished.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session closure for a research or code repository. Records what changed into the project's own handoff and log files, separating verified work from work merely attempted, and reports what is left uncommitted. Use when wrapping up a session so the next one can resume without re-deriving state. Its start-of-session twin is sitrep.
日本語の概要は準備中です。原文の説明を表示しています。
Opens a deliverable (talk, course module, paper, book chapter, or referee report) for AI-assisted work across sessions. Interviews the author for the manifest, then scaffolds deliverable.yml, an append-only HANDOFF.md, a numbered planning/ wiki with open questions, an inbox/ for dictated braindumps, a gitignored checks/, and the house deck template for talks. Use when starting deadline-driven work that spans sessions, or when asked to open a deliverable, set up a talk, paper, or module for the pipeline, or make a manifest. Not for one-off tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Review pytest test effectiveness against authoritative contracts, relevant faults, behavior-preserving refactors, realistic boundaries, isolation, and diagnostics. Use for test-quality audits, coverage-gap reviews, regression-test changes, or mocking reviews; preserve existing project gates rather than inventing coverage targets.
日本語の概要は準備中です。原文の説明を表示しています。
Guides pytest test architecture for Python 3.11+ using behavioral contracts, risk, and maintenance-adjusted value. Use when choosing unit/integration/property/e2e boundaries, fixture strategy, coverage measurement, or mutation testing. Preserves existing project gates but does not invent test-pyramid ratios, coverage percentages, mutation-score targets, or tests for implementation detail.
日本語の概要は準備中です。原文の説明を表示しています。
Provides Hatchling build backend guidance for Python packaging — use when configuring pyproject.toml metadata, build targets (wheel, sdist, binary), file selection with git-style globs, build hooks, metadata hooks, version management (code/regex/env sources), editable installs, the hatch-vcs plugin, plugin development, build environment setup (UV/pip/Cython), setuptools migration, or troubleshooting Hatchling errors. Covers PEP 517/518/621/660 standards and context variable interpolation.
日本語の概要は準備中です。原文の説明を表示しています。
Python web and API development enforcing strict route/domain/data layer separation, Pydantic v2 strict request-response models, edge-resolved auth, and async-safe HTTP clients. Use when working with FastAPI, Starlette, Django, Flask, HTTP endpoints, request models, authentication flows, async handlers, or any Python web framework task.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize existing CLAUDE.md, SKILL.md, agent definitions, and other AI-facing files for Claude comprehension and economy. Scope: optimization of existing content only — not upstream sync, not read-only auditing. Measures baseline metrics, delegates to the ai-doc-optimizer agent with file-type-specific context, runs independent verification via second agent, measures post-optimization metrics, and presents comprehensive before/after report. Supports iterative mode for large targets. Use when improving prompt effectiveness, reducing token waste, or rewriting instructions for LLM consumption. Invoke with /optimize-claude-md <file-or-directory>.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating Claude Code plugin hooks — language selection heuristic (Node.js default, match project runtime when obvious), hooks.json configuration, event selection, prompt-based vs command hooks, ${CLAUDE_PLUGIN_ROOT} paths, stdio suppression, timeout sizing, and testing. Use when adding hooks to a plugin, creating PreToolUse/PostToolUse/Stop/SubagentStop/SessionStart/UserPromptSubmit hooks, or wiring hook scripts to hooks.json.
日本語の概要は準備中です。原文の説明を表示しています。