「actors」の検索結果

This skill determines whether inpatient diabetic patients meet high-risk criteria for CGM initiation using Table 3 factors such as age ≥65 years, BMI ≤27 kg/m², type 1 diabetes, insulin regimen, and specific clinical conditions. It is triggered by clinician questions like "Should I assess this inpatient for CGM initiation based on hypoglycemia risk?" or "Is this patient a candidate for inpatient CGM?"

日本語の概要は準備中です。原文の説明を表示しています。

Guidance for clinicians managing pregnant individuals with preexisting diabetes mellitus (PDM) who are evaluating daily carbohydrate intake; consider a carbohydrate-restricted diet (<175 g/day) or usual diet (>175 g/day) based on patient factors. Trigger when assessing nutrition in pregnancy for PDM, especially when discussing glycemic targets, weight gain, or fetal growth concerns.

日本語の概要は準備中です。原文の説明を表示しています。

This skill directs lifelong treatment of cardiovascular risk factors, osteoporosis, and psychiatric symptoms in all patients with Cushing's syndrome until biochemical resolution of hypercortisolism. Use when managing any CS patient for long‑term comorbidity control; triggers include persistent hypertension, dyslipidemia, low bone density, depression, anxiety, or cognitive changes in the setting of known or suspected CS.

日本語の概要は準備中です。原文の説明を表示しています。

Guides choice among spironolactone, eplerenone, and esaxerenone for primary aldosteronism based on comparative efficacy, safety, and patient-specific factors. Triggers include when initiating MRA therapy and asking 'Which MRA should I prescribe?' or considering switching agents due to adverse effects, cost, or need for potassium supplementation.

日本語の概要は準備中です。原文の説明を表示しています。

This skill provides criteria to distinguish unilateral from bilateral primary aldosteronism using adrenal venous sampling results, including lateralization index, contralateral ratio, and clinical factors. It is triggered after AVS when clinicians analyze results and ask 'Is this unilateral or bilateral PA?' or need to guide treatment decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Recommends checking and managing vitamin D according to Endocrine Society guidelines to avoid hypocalcemia in patients receiving bisphosphonates or denosumab for hypercalcemia of malignancy. Use when a clinician notes risk factors for hypocalcemia (e.g., low 25‑OH vitamin D, renal insufficiency) and asks about baseline labs before antiresorptive start.

日本語の概要は準備中です。原文の説明を表示しています。

Determines whether to recommend adrenalectomy or mineralocorticoid receptor antagonists for primary aldosteronism based on PA subtype and patient/surgical factors. Triggered after subtype confirmation when clinicians ask “Should this patient have surgery or medical treatment?” or discuss treatment options with the patient.

日本語の概要は準備中です。原文の説明を表示しています。

Work a primary-prevention patient through the 2026 ACC/AHA multisociety dyslipidaemia guideline CPR framework — Calculate (10-year and 30-year PREVENT-ASCVD), Classify (low / borderline / intermediate / high), Personalize (demographic, clinical, biomarker, and reproductive risk enhancers), and Reclassify (coronary artery calcium scoring where appropriate). Use when a clinician asks how to assess ASCVD risk for primary prevention, who needs a statin, borderline risk patient what to do, intermediate risk should I start a statin, risk enhancers to look for, premature family history of ASCVD how does it change risk, pregnancy-related risk factors, PCOS and cardiovascular risk. Grounded in the 2026 ACC/AHA multisociety dyslipidaemia guideline.

日本語の概要は準備中です。原文の説明を表示しています。

Set absolute LDL-C, non-HDL-C, and ApoB treatment goals, PLUS percent LDL-C reduction, for a primary-prevention patient on lipid-lowering therapy per the re-introduced treatment goals in the 2026 ACC/AHA multisociety dyslipidaemia guideline. Covers goals by PREVENT-ASCVD category (low / borderline / intermediate / high), by CAC score, in severe hypercholesterolaemia / FH, in diabetes with multiple ASCVD risk factors, and the ApoB targets once LDL-C and non-HDL-C goals are met. Use when a clinician asks what LDL goal to aim for, LDL target for intermediate risk, non-HDL goal, ApoB target, dual goals on statin, patient at goal or not, how low should LDL go, statin not enough what next. Grounded in the 2026 ACC/AHA multisociety dyslipidaemia guideline.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.

日本語の概要は準備中です。原文の説明を表示しています。

AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.

日本語の概要は準備中です。原文の説明を表示しています。

Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.

日本語の概要は準備中です。原文の説明を表示しています。

Automate web scraping and data extraction with Apify -- run Actors, manage datasets, create reusable tasks, and retrieve crawl results through the Composio Apify integration.

日本語の概要は準備中です。原文の説明を表示しています。

Scrape leads from multiple platforms using Apify Actors.

日本語の概要は準備中です。原文の説明を表示しています。

Keep a small requested change focused when optional refactors, architectural redesign, or unrelated cleanup threaten to expand its scope.

日本語の概要は準備中です。原文の説明を表示しています。

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

日本語の概要は準備中です。原文の説明を表示しています。

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

日本語の概要は準備中です。原文の説明を表示しています。

Expert-level reaction engineering covering reaction kinetics, reactor design, ideal and non-ideal reactors, catalysis, and reactor scale-up.

日本語の概要は準備中です。原文の説明を表示しています。

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

日本語の概要は準備中です。原文の説明を表示しています。

Use when tracing the root cause of a resolved incident or recurring bug — 5-whys chain, fishbone categorisation, contributing-factors split — even if the user says 'why does this keep breaking?'.

日本語の概要は準備中です。原文の説明を表示しています。

Writes or edits PHP code — controllers, classes, type hints, SOLID refactors, modern idioms — even without naming PHP. NOT for writing tests (use pest-testing) or explaining PHP concepts.

日本語の概要は準備中です。原文の説明を表示しています。

When the user says 'refactor this', 'rename class', or 'move method'. Safely refactors code in any language — finds all callers, updates downstream dependencies, verifies via quality tools.

日本語の概要は準備中です。原文の説明を表示しています。

Maintains repo-local action contracts and harness repositories where product CLI and MCP adapters stay thin over core libraries. Use when adopting or improving steward.yaml actions, capability-level adoption evidence, cold-start proof loops, probes, benchmarks, CLI/MCP/core parity, adapter refactors, packages/core boundaries, or sibling harness layout; use repo-quality-system-lifecycle first for general app/library/tool stewardship baselines.

日本語の概要は準備中です。原文の説明を表示しています。