5,171 件 ・ 関連度順
Set up and launch CLED, the ambient keyboard daemon that shows your Claude Code agents' status on your keyboard via OpenRGB. Use when the user asks to start, launch, run, or set up CLED.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses patient’s understanding of how CGM data (trends, rates of change) differ from discrete SMBG fingerstick values. Triggered when clinicians hear requests to explain lag and trend arrows on CGM or teach the difference between CGM glucose and fingerstick glucose.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends transsphenoidal selective adenomectomy (TSS) by an experienced pituitary surgeon as the optimal treatment for Cushing's disease in pediatric and adult patients. Use when a patient with ACTH-dependent Cushing syndrome is a surgical candidate; triggers include overt Cushing's syndrome, elevated UFC or late-night salivary cortisol, and pituitary MRI showing an adenoma.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends using radiation therapy for corticotroph adenomas in Cushing's disease when imaging shows invasive features or mass‑effect concerns such as cavernous sinus invasion, suprasellar extension, or knobby protrusion. Consider RT when postoperative medical therapy has normalized cortisol but tumor progression or residual invasive disease is suspected.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests repeat transsphenoidal surgery for patients with persistent hypercortisolism after initial transsphenoidal surgery when imaging shows evidence of incomplete resection or a pituitary lesion. Clinical triggers include postoperative MRI revealing residual adenoma, persistent elevated UFC or late-night salivary cortisol, and visible pituitary lesion on imaging.
日本語の概要は準備中です。原文の説明を表示しています。
Determines the appropriate IV pamidronate dose (60‑90 mg) and infusion duration (2‑24 h) for adults with hypercalcemia of malignancy based on renal function. Triggered when a clinician orders pamidronate and asks how to adjust for kidney dysfunction (eGFR < 60 mL/min/1.73 m²).
日本語の概要は準備中です。原文の説明を表示しています。
Adjusts intravenous bisphosphonate dosing and infusion duration for patients with hypercalcemia of malignancy and renal insufficiency (creatinine clearance <60 mL/min). Triggered when a clinician encounters renal impairment and asks how to modify zoledronic acid or pamidronate infusion rates.
日本語の概要は準備中です。原文の説明を表示しています。
Provides a checklist of five evidence-based measures to enhance the technical success of adrenal venous sampling procedures. Triggers include when preparing for AVS and asking 'How can I maximize success rate?' or troubleshooting failed attempts.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods.
日本語の概要は準備中です。原文の説明を表示しています。
Show stored output for a Claude Companion job.
日本語の概要は準備中です。原文の説明を表示しています。
Research the codebase to answer a question without making any changes. Use when exploring code, understanding architecture, or investigating how something works.
日本語の概要は準備中です。原文の説明を表示しています。
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
日本語の概要は準備中です。原文の説明を表示しています。
Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic", "design this", "theme this", "use my brand", "iterate on this design", "review this artifact", "make this bolder", "make this quieter", "simplify this design", "animate this", "improve the look of", "give this a refresh"). Captures brand from the user's codebase, asking, or live site, then applies it to every artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Produce 3+ distinct hi-fi design variations — basic to bold, one file with tweak controls — when the user asks for options, alternatives, "show me a few takes". Extends fe-design.
日本語の概要は準備中です。原文の説明を表示しています。
Use when classifying data, setting retention, judging cross-border transfer, or shaping DSR workflow. Triggers on 'how long do we keep this', 'can this data go to the US'.
日本語の概要は準備中です。原文の説明を表示しています。
The kpopper method: a knowledge record (GROUNDING.yaml) for work that gets revisited - what is known, where each piece came from, and what would make each conclusion wrong. Use when asked what kpopper is or how to keep a record, when choosing which kpopper skill fits a moment, or when no narrower one does. The occasions have their own skills: ground (read the record before answering), record (write what the work found), map (map existing materials), annotated-doc (a standalone HTML document with evidence), hub (the record's visual home), consolidate (hypotheses and merges), watch (background checks).
日本語の概要は準備中です。原文の説明を表示しています。
Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
日本語の概要は準備中です。原文の説明を表示しています。
Pull the latest GEO-SEO skill updates from the upstream repository. Compares installed files against the latest release, shows what changed, and updates all skills, agents, scripts, and schema templates in place.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality gates) and the review-specific checks that code alone can't show
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. Use it proactively when an existing skill could be a ready-made building block, while keeping installation scoped to the current project unless the user explicitly requests a global install.
日本語の概要は準備中です。原文の説明を表示しています。
Reading a GLSL compiler's log, mapping its line numbers to your source, telling "compiles" from "draws", and the triage order for a black canvas. Read this when a shader fails in a way that does not make sense, or when it compiles and still shows nothing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, map, or restructure a website's page hierarchy, navigation, URL structure, or internal linking — "sitemap," "information architecture," "IA," "breadcrumbs," "what pages do I need," "how should I organize my site." NOT for XML sitemaps (technical SEO — see seo-audit). For structured data, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。