7,433 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
This skill suggests pituitary-directed medical treatments (e.g., cabergoline, pasireotide) for patients with Cushing's disease who are not surgical candidates or have persistent disease after transsphenoidal surgery. Use when a CD patient cannot undergo surgery or has residual disease post-TSS; triggers include "not a surgical candidate", "persistent disease after TSS", "ongoing hypercortisolism despite prior surgery".
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends obtaining serum free T4 and prolactin levels within 1–2 weeks after transsphenoidal surgery (TSS) for Cushing's syndrome to screen for overt hypopituitarism. Use in postoperative Cushing's syndrome patients during the early recovery window when evaluating for new pituitary hormone deficiencies.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends localizing and resecting ectopic ACTH-secreting tumors with node dissection when ectopic ACTH secretion is suspected or confirmed. Clinical triggers include unexplained persistent hypercortisolism after pituitary surgery, elevated ACTH with negative pituitary MRI, or identification of occult ectopic ACTH syndrome (EAS) on biochemical testing.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends obtaining a postoperative pituitary MRI within 1–3 months after successful transsphenoidal surgery (TSS) to establish a new baseline for future recurrence assessment. Use when a Cushing’s syndrome patient has achieved biochemical remission post‑TSS and is entering routine follow‑up.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends regularly evaluating for corticotroph tumor progression using pituitary MRIs and ACTH levels in patients with known Cushing's disease who underwent bilateral adrenalectomy and in patients undergoing this procedure for presumed occult ectopic ACTH secretion. Triggers include postoperative follow‑up after bilateral adrenalectomy, rising ACTH levels, or new pituitary lesion on MRI suggestive of tumor progression.
日本語の概要は準備中です。原文の説明を表示しています。
Establishes age- and gender-specific blood pressure goals for pediatric patients with primary aldosteronism (PA) using published normative data to assess treatment adequacy and avoid over-treatment. Use when managing hypertension in children with PA to evaluate if BP is adequately controlled; triggers include pediatric PA hypertension, BP not normalized with glucocorticoid therapy, and need for age‑specific BP targets.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends initiating hydrocortisone replacement at a total starting dose of 8 mg/m2 body surface area per day, given in three or four divided doses, for children with confirmed primary adrenal insufficiency (PAI). Use when starting glucocorticoid therapy in pediatric PAI patients, adjusting the dose according to individual clinical response, growth, and need for stress coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests testing HPA axis functionality before and after starting GH replacement in patients not receiving glucocorticoid replacement with apparently normal pituitary-adrenal function. Triggers include initiating GH replacement in a GHD patient who is not on glucocorticoids and has normal adrenal function.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous experiment loop that optimizes any file by a measurable metric. Inspired by Karpathy's autoresearch. The agent edits a target file, runs a fixed evaluation, keeps improvements (git commit), discards failures (git reset), and loops indefinitely. Use when: user wants to optimize code speed, reduce bundle/image size, improve test pass rate, optimize prompts, improve content quality (headlines, copy, CTR), or run any measurable improvement loop. Requires: a target file, an evaluation command that outputs a metric, and a git repo.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Amazon product, sales, Amazon Ads, retail-readiness, and Best Seller Rank data to find commercially actionable growth opportunities. Use when Codex needs to identify which ASINs, campaigns, keywords, search terms, product targets, placements, categories, or BSR movements deserve more investment, optimization, harvesting, bid/budget changes, retail-readiness fixes, investigation, protection, or controlled scaling across Sponsored Products, Sponsored Brands, Sponsored Display, search term reports, targeting reports, campaign reports, placement reports, advertised/purchased product reports, Business Reports, organic performance, and BSR history.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose why Amazon advertising performance declined for a product, ASIN, campaign, marketplace, or account. Use when the user asks why sales, orders, ROAS, ACOS, TACoS, profit, BSR, rank, traffic, conversion rate, or campaign performance dropped, asks for dropped campaigns, says investigate drop/drop analysis, or asks about wasted spend, negative keywords, negative targets, keywords, targets, or search terms in a drop context.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when asked about "hooks", "PreToolUse", "PostToolUse", "SessionStart", "hook events", "validate tool use", "block commands", "add context on session start", or implementing event-driven automation.
日本語の概要は準備中です。原文の説明を表示しています。
Start the Wasp dev server and set up full debugging visibility. This includes running the server (with access to logs), and connecting browser console access so the agent can see client-side errors. Essential for any development or debugging work.
日本語の概要は準備中です。原文の説明を表示しています。
Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
Scans CopilotKit's public product / pricing / Premium pages at the start of every weekly report to produce the authoritative list of COMMERCIAL surfaces (Premium · CopilotKit Enterprise · Intelligence Platform · paid tiers) and detect any newly-added or changed commercial feature since last week. This list defines what the report's 🏢 Enterprise section is about — CopilotKit's commercial/paid product, NOT "CopilotKit running inside an enterprise company." Emits the surface list + a free-vs-paid classifier the report uses to decide "does this issue hit a commercial surface?", plus a diff of what changed. Runs as a subagent (many web fetches) so the orchestrator's context stays small. Invoked by weekly-report (spawned at report start) and the enterprise skill; also triggers on "scan product surfaces", "what's premium", "commercial surfaces", "did we add a premium feature".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to drive a research question (RQ) end-to-end: validate the RQ README, generate a fill batch-plan, start the Docker batch in the background, monitor progress, run aggregation, and propose findings updates. Trigger when the user says "RQ-N voranbringen", "run-rq", "fill RQ-N", "run RQ-N", "Forschungsfrage N starten", or names a specific RQ-N directory in research/.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level stellar physics covering stellar structure and evolution, nucleosynthesis, stellar atmospheres, variable stars, binary systems, and stellar populations.
日本語の概要は準備中です。原文の説明を表示しています。
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
日本語の概要は準備中です。原文の説明を表示しています。
Map existing materials into a first knowledge record, or investigate a subject's history in depth. Use whenever the user asks to map, survey, go through, reconstruct or investigate what already exists - folders of documents, decision records, meeting notes, emails, exports, code - or wants a starting record built from existing materials, even when the word 'record' is never said: consult this before listing or reading the files yourself, because a map has an agreed scope, a protocol and a report. Also, once, at a suitable moment, to offer the starting choices where a workspace has no record and the work is clearly ongoing - never on a greeting. Learning while working needs no map. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.
日本語の概要は準備中です。原文の説明を表示しています。
[Implementation] Use when you need to analyze and fix issues [INTELLIGENT ROUTING]. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix; --target=types resolves TypeScript errors inline.
日本語の概要は準備中です。原文の説明を表示しています。