2,108 件 ・ 関連度順
概要と使いどころ
Build an interactive account org chart, leadership map, buying committee, or manager/report neighborhood around a person. Use for decision makers, reporting-line candidates, stakeholder mapping, and warm intro paths. Skip standalone email lookup and unrelated cross-company prospecting.
日本語の概要は準備中です。原文の説明を表示しています。
The **Coherence Composer** is an epistemological skill that validates structural consistency and explores counterfactual worlds while respecting constraints from both **Commitment Tracker** (ontology) and **Opacity Detector** (epistemology).
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or backfilling AI-categorized daily GitHub releases from branch commits.
日本語の概要は準備中です。原文の説明を表示しています。
Configures pyproject.toml and Python packaging using PEP 517/518/621/660/723 standards. Use when creating or updating pyproject.toml, selecting a build backend (hatchling/setuptools/flit), configuring ruff, ty, mypy, pytest, or coverage tool sections, setting up dependency constraints or optional extras, defining CLI entry points, configuring pre-commit hooks, establishing src-layout directory structure, or preparing a package for PyPI publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Python tooling — uv package management, Hatchling build backend, ty or mypy type checker configuration, ruff linting, pre-commit hook setup, TOML read-write with tomlkit or tomllib, or PyPI packaging and release workflows. Routes to standalone specialist skills for deep dives on any single tool.
日本語の概要は準備中です。原文の説明を表示しています。
Routes Python engineering tasks to specialist skills by matching trigger patterns before any architecture, plan, or code is written. Use when working with Typer CLI frameworks, Rich or Textual terminal UIs, CLI UI/UX design, questionary prompts, FastMCP/MCP servers, ty type checker, uv package manager, Hatchling build backend, TOML editing, pre-commit/prek hooks, async Python, PyPI packaging, complex linting, technical debt modernization, testing workflows, feature development, or stdlib-only scripting.
日本語の概要は準備中です。原文の説明を表示しています。
Use when checking skill quality, validating frontmatter before commit, or diagnosing validator warnings. Runs the plugin validator on a skill, agent, or plugin directory — reports token complexity, broken links, frontmatter issues, and structural problems. Pass the path as an argument.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous self-assessment checklist before marking any task as complete. Use when about to claim task completion, before final commit, when user asks "is it done?", or when transitioning from implementation to reporting. Prevents premature completion claims by requiring evidence for every assertion.
日本語の概要は準備中です。原文の説明を表示しています。
Bulk-refresh research entries in ./research/ using parallel research-curator agents. Use when /refresh-research is invoked, stale research needs updating, or bulk re-verification of research entries is requested. Inventories entries by review date and age, runs RT-ICA pre-flight, spawns agents in waves of 5, then validates, reviews, and commits through research-curator. Supports --all, --stale, --category, --layer, and --dry-run flags.
日本語の概要は準備中です。原文の説明を表示しています。
Modern Git workflows, best practices, and commands. Use when the user asks about Git branch management (git switch vs checkout), file restoration (git restore), fixup commits, autosquash rebasing, git worktrees, rerere, force-with-lease, repository cleanup (git clean, stale branches, bloat analysis), history navigation (revision syntax, range notation, pickaxe search), recommended global git config, or GitButler and the but CLI.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.
日本語の概要は準備中です。原文の説明を表示しています。
Use when modifying agentic contextual building blocks like skills (SKILL.md), slash commands, agents, hooks, plugins, marketplaces, and instruction files (CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md, Cursor, Copilot, Cline, or Kiro rules), tool configuration such as an OpenCode `opencode.json`, Muse Code hooks (`.muse/hooks.json`), a Grok Build `.grok/` project layer or a Google Antigravity customization root (`.agents/`, `.agent/`, `_agents/`, `_agent/` — hooks, MCP config, rules, registries and plugins), and committed project memory (`.agents/memory/`). Run skillsaw on the files you touched, apply autofixes, resolve remaining violations with `skillsaw explain` guidance, and re-lint until clean before considering the work complete.
日本語の概要は準備中です。原文の説明を表示しています。
Update a repository to the newest skillsaw — upgrade the install, report new rules and their findings in your repo, and bump version pins (GitHub Action SHAs, Makefile targets, pre-commit hooks). Use when a new skillsaw release is out and you want its latest checks.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "update the changelog", "add a changelog entry", "write a CHANGELOG entry", or when preparing a git commit in StreamFlow that requires updating the `## [Unreleased]` section of `CHANGELOG.md`.
日本語の概要は準備中です。原文の説明を表示しています。
Consult an independent, read-only GPT-6 Astra advisor before committing to a substantive interpretation, approach, or final result. Not for routine work, implementation, or file edits. Uses gpt-6-astra at an effort matched to the question.
日本語の概要は準備中です。原文の説明を表示しています。
Generates 3-5 conceptually distinct approaches labeled Novel, Surprising, Diverse, or Conventional, and holds for the user's selection before implementing. The --codex mode runs the brainstorm on GPT-6 Astra via codex exec, then has Codex implement the selected approach. Use before committing to an approach when a creative, architectural, or analytical task has more than one non-obvious solution; use --codex when another model family should widen the range.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session closure. Records what changed into the project's own handoff and log files, separating verified from attempted work, and reports what is uncommitted. Use when wrapping up a session. Twin of sitrep.
日本語の概要は準備中です。原文の説明を表示しています。
Generates 3-5 conceptually distinct approaches (Novel, Surprising, Diverse, Conventional) and holds for selection before implementing. Use before committing to an approach when a task has more than one non-obvious solution; --codex delegates the brainstorm to a fresh subagent.
日本語の概要は準備中です。原文の説明を表示しています。
Consults Fable as an independent, read-only reviewer at an effort the caller matches to the question. The calling session (usually Opus, or Haiku) holds the task and escalates one decision point. Use before committing to an interpretation or a substantial piece of writing or analysis, when stuck or not converging, when changing approach, or as a final check on a finished task. Fallback for when the native advisor tool is unavailable. Not for a session already running Fable.
日本語の概要は準備中です。原文の説明を表示しています。
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a target someone has already committed to (a board plan, an annual plan, a contract) into a plan the team can measure: KPIs in three tiers with a guardrail for each, a baseline from real data, monthly pacing with lag and seasonality, and two or three channels chosen from how your ICP actually searches and buys. Writes context/goals/MMYY-scope.md and context/goals/measurement.md. It never invents the target. Triggers: "set our goals", "what are our KPIs", "revenue target and pacing", "which channels and what targets", "write the scope file", "are we on track". Run after /funnel-strategy. Not for designing funnel stages (use /funnel-strategy).
日本語の概要は準備中です。原文の説明を表示しています。
Day Open protocol. Collects yesterday's commits, issues, notes, calendar, bot QA, Scout, world events — builds DayPlan and compact dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
Detect AI/LLM-generated text patterns in research writing. Use when: (1) Reviewing manuscript drafts before submission, (2) Pre-commit validation of documentation, (3) Quality assurance checks on research artifacts, (4) Ensuring natural academic writing style, (5) Tracking writing authenticity over time. Analyzes grammar perfection, sentence uniformity, paragraph structure, word frequency (AI-typical words like 'delve', 'leverage', 'robust'), punctuation patterns, and transition word overuse.
日本語の概要は準備中です。原文の説明を表示しています。