7,682 件 ・ 人気順
概要と使いどころ
Audit a quoting or estimation system -- analyze labor hour estimation accuracy, material take-off completeness, pricing rule engines, markup and margin optimization, good-better-best tiered pricing, and quote-to-close win rates.
日本語の概要は準備中です。原文の説明を表示しています。
Audit laboratory automation systems -- LIMS architecture, instrument connectivity (SiLA 2, OPC-UA, serial drivers), sample tracking and chain of custody, protocol workflow engines, data acquisition pipelines, and regulatory compliance (21 CFR Part 11 electronic records/signatures.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze medical billing and revenue cycle management software including claims processing pipelines, EDI transaction handling (837P/837I/835/270/271/276/277), ICD-10 and CPT code validation with NCCI edit checking, payer rules engine configuration, denial management and appeal workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze disability services software — IEP and ISP management, person-centered planning workflows, HCBS Settings Rule compliance, accommodation tracking, assistive technology integration, EVV (Electronic Visit Verification), caregiver and DSP scheduling, and outcome measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze government benefits processing software for eligibility determination, application workflow efficiency, document verification, error rates, appeal tracking, multi-program coordination, and ADA/Section 508 compliance..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze bookkeeping automation systems for transaction categorization, bank reconciliation, AP/AR efficiency, chart of accounts optimization, and month-end close using GAAP and double-entry accounting patterns..
日本語の概要は準備中です。原文の説明を表示しています。
Generate a multi-channel abandoned cart recovery sequence — SMS at 15 min (98% open rate, 25-40% conversion) followed by email cadence at 1hr / 24hr / 72hr, plus optional push and retargeting touchpoints..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze insurance claims workflow systems for intake optimization, adjudication rules, subrogation, litigation management, and settlement analytics. Triggers: 'audit claims process', 'review FNOL workflow', 'evaluate claims automation', 'check subrogation recovery'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed Arsenal skills.
日本語の概要は準備中です。原文の説明を表示しています。
Write a product brief and its task list when the user requests a product specification. Never implement it.
日本語の概要は準備中です。原文の説明を表示しています。
Read and manage Calendly: list scheduled events, event types, invitees, and availability schedules; cancel bookings. Trigger phrases: calendly, my meetings, scheduled events, cancel booking.
日本語の概要は準備中です。原文の説明を表示しています。
List ClickUp workspaces and tasks, and create tasks. Trigger phrases: clickup, clickup tasks, my clickup list.
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Create complete, well-structured Copilot skills from scratch. USE FOR: scaffolding new SKILL.md files, writing effective agent instructions, configuring frontmatter fields, setting up directory structure (references, FEEDBACK.md), optimizing description for discoverability, applying progressive disclosure. DO NOT USE FOR: managing/syncing existing skills (use skill-manager-guide), general coding, VS Code extension development.
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Persist analysis so it survives context compression and chains between tasks. USE FOR: any task whose decisions affect future work — features, refactors, architecture changes, integrations. Produces a lightweight Task Analysis Map that externalizes intent, decisions, and chain context. Use to document decisions, create continuity, prevent context loss, bridge tasks, externalize reasoning. DO NOT USE FOR: quick intent validation (use task-intent), deep structured analysis (use contextação).
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Structured context analysis before acting. USE FOR: questioning assumptions, mapping dependencies, identifying blind spots, validating scope of any task or subject. Use to contextualize, question, analyze before implementing, review premises, prevent hallucination, structured assessment. DO NOT USE FOR: simple tasks where task-intent suffices, direct implementation, code review.
日本語の概要は準備中です。原文の説明を表示しています。
Read and manage Asana tasks: my tasks, task details, create tasks. Trigger phrases: asana, my tasks, task list, todo.
日本語の概要は準備中です。原文の説明を表示しています。
Create animated flow diagrams from articles, workflow notes, architecture sketches, or process descriptions using a JSON specification and a local Python/Pillow renderer. Use when the user wants to turn source material into a static PNG + animated GIF diagram.
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Create custom VS Code Copilot agents (.agent.md). USE FOR: new agents, tool restrictions, handoffs, orchestration patterns, discipline constraints. DO NOT USE FOR: general coding, VS Code extension development.
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Understand before implementing. USE FOR: any task where the agent might rush to code — forces understanding WHY/WHAT FOR/FOR WHOM before defining a solution, activates planning and reasoning discipline, prevents technical debt from shallow requests. Use to validate intent, plan before coding, reason before acting, challenge assumptions, prevent premature implementation. DO NOT USE FOR: deep multi-technology analysis (use contextação), persisting decisions across tasks (use task-map).
日本語の概要は準備中です。原文の説明を表示しています。
Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
日本語の概要は準備中です。原文の説明を表示しています。
Build a dated monthly or quarterly editorial calendar: which posts to publish or review when, content mix, templates, distribution timing, and a material-change review queue. Use when the user says "editorial calendar", "content calendar", "publishing schedule", "what should I write this month". Not for positioning or pillars (blog-strategy), SERP-validated cluster maps (blog-cluster), or detecting declining pages from Search Console exports (blog-decay). Publication frequency is not a ranking signal.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task, before touching code
日本語の概要は準備中です。原文の説明を表示しています。