1.2万 件 ・ 関連度順
概要と使いどころ
This skill recommends discussing and offering age-appropriate vaccinations (influenza, herpes zoster, pneumococcal) to patients with Cushing’s syndrome due to increased infection risk. Use when reviewing preventive care for a CS patient; triggers include discussing preventive care, vaccination status, or infection risk in a CS patient.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies safe antihypertensive options for hypertensive disorders in pregnancy applicable to PA patients, with gestational age restrictions. Triggers include when managing hypertension in a pregnant or pregnancy-planning PA patient and asking 'What BP meds are safe?' or reviewing medications.
日本語の概要は準備中です。原文の説明を表示しています。
Determines successful catheterization in adrenal venous sampling by applying selectivity index cut‑offs with and without ACTH stimulation. Triggered during AVS when measuring cortisol levels and asking “Is the catheter properly positioned?” or when reviewing results for technical adequacy.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends potassium supplementation for hypokalemia management in PA patients who are pregnant or planning pregnancy. Triggered when a pregnant PA patient presents with low serum potassium and asks 'How should I treat hypokalemia?' or when electrolytes are reviewed.
日本語の概要は準備中です。原文の説明を表示しています。
This skill interprets the oral sodium loading test for primary aldosteronism by evaluating 24‑hour urinary aldosterone excretion after a high‑sodium diet. Use when reviewing results of an "oral sodium loading test" for PA diagnosis; trigger phrases include "urinary aldosterone excretion ≤10 g/24 h" (PA unlikely) or "≥12 g/24 h (Mayo) / ≥14 g/24 h (Cleveland)" (PA highly likely).
日本語の概要は準備中です。原文の説明を表示しています。
Suggests that pregnant patients with primary adrenal insufficiency be monitored for clinical signs of glucocorticoid over- or under-replacement such as normal weight or gain, fatigue, postural hypotension or hypertension, and hyperglycemia, with at least one review each trimester. Use when managing a pregnant patient with PAI to assess glucocorticoid dosing adequacy.
日本語の概要は準備中です。原文の説明を表示しています。
Determines if primary aldosteronism is confirmed based on upright plasma aldosterone ≤6 ng/dL (170 nmol/L) on day 4 at 10 AM of fludrocortisone suppression test, provided plasma renin activity ≥1 ng/mL/h and plasma cortisol concentration lower than the 7 AM value to exclude ACTH confounding. Use when reviewing FST results to diagnose PA; triggers include "FST", "upright aldosterone ≤6 ng/dL", "PRA ≥1 ng/mL/h", and "cortisol drop".
日本語の概要は準備中です。原文の説明を表示しています。
Differentiates aldosterone-producing adenoma from idiopathic adrenal hyperplasia based on 18-hydroxycorticosterone levels, with APA patients generally having levels >100 ng/dL at 8:00 a.m. and IAH patients usually having levels <100 ng/dL. Use when reviewing 18-OHB test results to help subtype PA; triggers include 18-OHB >100 ng/dL (suggesting APA) or <100 ng/dL (suggesting IAH).
日本語の概要は準備中です。原文の説明を表示しています。
Reconcile baseline-versioned files that the `create-baseline upgrade` CLI staged for LLM-assisted semantic merge. Use when the CLI prints "Open Claude Code and run /upgrade-project to reconcile". Reads the stage manifest at `.claude/state/upgrade/<ts>/manifest.json`, reasons through each pending file's three-way delta in main context, writes a reconciled LOCAL, then deletes the stage when every file lands. Supports `--dry-run` (preview the reconciled diff without writing) and a structured "needs-user-input" fallback when the conflict cannot be disambiguated automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow Phase 7 — Mechanical cleanup pass over the branch diff, followed by a `code-structure` review pass and a `verify` re-stamp. Shadows the global `simplify` skill at project scope; the cleanup pass is performed inline rather than via Skill self-call.
日本語の概要は準備中です。原文の説明を表示しています。
Extract every PlantUML block from docs/specs/<slug>.md and render each to SVG under docs/specs/_rendered/<slug>/, with an index.md listing them in order. Run this before /approve-direction so the reviewer sees pictures instead of raw PlantUML.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use for SWOT analysis, or when the user wants to assess where a team, product or company stands: "strengths and weaknesses", "should we enter this market?", "review our position", "competitor comparison". Turns findings into actions. Skip for detailed planning or pure market sizing.
日本語の概要は準備中です。原文の説明を表示しています。
Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.
日本語の概要は準備中です。原文の説明を表示しています。
把商品原图与生成图对照，检查形状、部件、标识和文字有没有改错，并指出具体问题。用于上架前检查或判断图片是否失真；只要求检查时不自动改图。
日本語の概要は準備中です。原文の説明を表示しています。
小说逻辑/剧情审查，适用于用户说"帮我检查下小说有没有bug"、"看看时间线有没有矛盾"、"人物有没有OOC"、"找剧情前后冲突"、"梳理伏笔有没有回收"、"检查小说剧情合理性"、"看看有没有剧情漏洞"、"人物行为不符合性格"、"检查时间线对不对"、"找小说前后矛盾的地方"、"帮我梳理所有伏笔"、"小说剧情bug检查"、"逻辑漏洞排查"等需求，检测时间线冲突、逻辑漏洞、人物OOC、伏笔遗漏等问题，**执行字数检查确保章节字数达标**，**生成详细问题清单并自动修复所有问题，修复结果直接修改 chapters/ 目录，修改前自动备份到 .webnovel/write/original/**，**批量审查时使用子Agent并行处理，每个Agent最多负责3个章节**
日本語の概要は準備中です。原文の説明を表示しています。
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a written implementation plan to execute in a separate session with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。