7,944 件 ・ 関連度順
概要と使いどころ
Automated cell behavior analysis from microscopy or XR lab recordings. Classifies cell motion phenotypes (migration, proliferation, apoptosis, division, quiescence), computes population-level quantitative metrics (growth rate, migration velocity, directionality index), and emits structured JSON for downstream reporting, plotting, or ELN integration.
日本語の概要は準備中です。原文の説明を表示しています。
Given an article DOI or PubMed ID, discover and download the genomics data files deposited by the authors (VCF, FASTA, H5AD, CSV, JSON, BAM, etc.) from public repositories such as GEO, ENA, Zenodo, Figshare, Dryad, and OSF.
日本語の概要は準備中です。原文の説明を表示しています。
This skill determines whether an adolescent or adult patient meets DSM-5 criteria for gender dysphoria (gender incongruence) by evaluating the presence of at least two of six specified criteria over a minimum 6-month duration, accompanied by clinically significant distress or impairment. It is triggered when a clinician queries whether the patient's reported symptoms align with gender dysphoria, such as persistent incongruence between experienced/expressed gender and designated gender.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically interpret a Medtronic CareLink or MiniMed 780G Daily Review download in a structured 6-step clinical workflow — covering Time in Range, insulin delivery, day/night patterns, hypo and hyperglycemia root causes, and a prioritised action plan. Trigger when a clinician uploads or shares a CareLink report, MiniMed download, 780G Daily Review, pump download, or asks to review a patient's CGM or insulin pump data.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends educating patients and families about the clinical features of remission in Cushing's syndrome when a patient achieves biochemical remission after treatment. Use when a CS patient has postoperative normal cortisol levels, reports symptom improvement, and requires guidance on long-term expectations and monitoring for recurrence.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests a trial of dehydroepiandrosterone (DHEA) replacement in women with primary adrenal insufficiency (PAI) who report low libido, depressive symptoms, and/or low energy levels despite otherwise optimized glucocorticoid and mineralocorticoid replacement. Consider when a woman with PAI presents with persistent low libido, depressive symptoms, and/or low energy levels after glucocorticoid and mineralocorticoid doses have been titrated to clinical targets.
日本語の概要は準備中です。原文の説明を表示しています。
Initiates a 6‑month trial of DHEA replacement in women with primary adrenal insufficiency (PAI) who have persistent low libido, depressive symptoms, or low energy despite otherwise optimized glucocorticoid and mineralocorticoid therapy. If the patient does not report a sustained beneficial effect after 6 months, discontinue DHEA.
日本語の概要は準備中です。原文の説明を表示しています。
The Endocrine Society guideline recommends against routine hormonal monitoring of glucocorticoid replacement in primary adrenal insufficiency and advises adjusting therapy solely based on clinical response. Use when evaluating glucocorticoid dose adequacy, such as when patients report fatigue, weight loss, hypotension, or signs of Cushingoid over-replacement.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests using longer-acting glucocorticoids when standard hydrocortisone regimens are impractical due to nonavailability, poor adherence, or need for once-daily dosing. Triggers include glucocorticoid replacement therapy decisions where patients report difficulty with multiple daily doses, lack of access to hydrocortisone, or preference for simplified regimens.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a swarm plan wave by wave with filesystem isolation via git worktrees. For each wave, main context decides the scenario recipe + implementation contract for every task, then spawns one swarm-worker per task in parallel. Each worker executes its recipe and reports JSON status. Worktree merge-audit verifies write-set discipline before changes land on main. Aborts remaining waves on any audit or task failure.
日本語の概要は準備中です。原文の説明を表示しています。
Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates `impeccable` for every design task inside a workflow phase. Captures intent in natural language, classifies it (design / development / copy), translates design intents into a sequence of impeccable subcommand invocations, runs them in main context with state persistence at `.claude/state/design/<slug>.json`, and returns a structured report. ALWAYS invokes `impeccable` under the hood for the underlying design move; never picks aesthetic direction itself; never writes product code directly. Per CLAUDE.md Article X.2, all design tasks in workflow phases route through this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap the central system spec at `docs/system/` for a repository that has never had one. Scans the governed surface, proposes a concept map clustered by directory, and materializes elements + shards ONLY after a human confirms that map. Use when adopting the baseline on an existing project, or when the corpus needs re-deriving from scratch. Re-runnable. Requires `memory.architecture_map.enabled` and a declared `governed_surface`.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow Phase 8 (optional) — OWASP-aligned security review of pending code changes. Produces a prioritized findings report (Critical/High/Medium/Low) mapped to OWASP Top 10 and CWE IDs. Output at `docs/security/<slug>-<date>.md`. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Dev-only check that a drafted spec for THIS baseline repo won't ship dev-tree references to consumer installs. Catches three failure modes — shipped SKILL.md prose that references paths under `src/`, `tests/`, `scripts/`, `obj/` as runtime invocations (in ```bash fences``` OR `inline backticks`, plus shipped `.mjs`/`.js`/`.sh`/`.py` helper-file imports); new Python helpers added under `.claude/skills/<slug>/` (shipped helpers must be `.sh` or `.mjs`/`.js` going forward); and imports of modules that aren't in `obj/template/.claude/manifest.json` (consumer won't have the file). The aggregate scanner (`scan-shipped-skills.mjs`) walks only baseline-owned skill dirs (via `owner: baseline` frontmatter) at top level — `references/` and other subdirs are documentation, not runtime. BLOCKER findings hard-block implementation entry; ADVISORY surfaces but doesn't block. Read-only — surfaces a punch list; maintainer edits the spec and re-runs until CLEAN.
日本語の概要は準備中です。原文の説明を表示しています。
Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.
日本語の概要は準備中です。原文の説明を表示しています。
Review the auto-extracted candidates in `.claude/memory/_pending.md` and commit keepers to the canonical memory files (`landmarks.md`, `libraries.md`, `decisions.md`, `landmines.md`, `conventions.md`, `pending-questions.md`, `backlog.md`). Invoke at session start when the SessionStart hook reports pending candidates, or any time `_pending.md` has accumulated entries you want to curate. Reset the pending body after flushing.
日本語の概要は準備中です。原文の説明を表示しています。
EXPERIMENTAL. Join or leave an org-team coordination channel as a session peer. `/companion on <channel_id> [peer_id]` registers this Claude Code session as a `pclass:"session"` peer and works the claim → execute → signal loop, escalating un-decidable forks to the lead (never deciding). `/companion off` deregisters. `/companion status` reports the current peer. Part of org mode (Article X), which is opt-in via `velocity.org_mode.enabled` and OFF by default. Use when a human launches a second session to act as a peer alongside a lead.
日本語の概要は準備中です。原文の説明を表示しています。
A guided agent security review of amux, its CI/CD, and repo.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
日本語の概要は準備中です。原文の説明を表示しています。
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
日本語の概要は準備中です。原文の説明を表示しています。
Author in-repo SKILL.md: frontmatter, validator, structure.
日本語の概要は準備中です。原文の説明を表示しています。