Results for “protocol”

Use when a task needs the judgment of a Clinical Research Coordinator — managing patient recruitment/enrollment against a trial's screen-fail rate, handling a protocol deviation, tracking informed consent and regulatory documentation, or coordinating a multi-visit study schedule against patient retention risk.

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of a Biology Professor at a research university — writing or defending an NIH/NSF grant budget, deciding authorship order on a paper, navigating an IACUC or biosafety protocol, mentoring a PhD student through a stalled project, or converting a course when active-learning data doesn't match student pushback.

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of a Biostatistician — designing a clinical trial's sample size and analysis plan, choosing a survival-analysis or censoring-aware method, preparing a DSMB safety readout, or judging whether a trial's efficacy claim survives ITT vs. per-protocol scrutiny.

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of an Animal Control Worker — responding to a dog-bite or animal-attack call, determining rabies-exposure quarantine protocol, evaluating a dangerous-dog classification referral, planning a cruelty/neglect investigation and removal, or selecting a capture/restraint method for a stray or wildlife-in-structure call.

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of an Animal Caretaker — triaging daily husbandry when kennel census exceeds staffing capacity, reading a Fear-Anxiety-Stress (FAS) score change or appetite/output drop against an escalation threshold, deciding brush-out vs. shave-down on a matted coat, or setting isolation and vaccination-lead-time protocol for a new intake or boarding admission.

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of an animal trainer — designing a behavior-modification plan for a specific problem behavior, choosing a reinforcement schedule and deciding when to raise criteria, structuring session length and frequency to avoid fatigue or frustration plateaus, or setting a handler/public safety protocol around a training animal.

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of a livestock geneticist/animal breeder — selecting a sire against EPDs or genomic data, screening a proposed mating for inbreeding risk, deciding AI versus natural service, timing an estrus-synchronization protocol, or defending a breeding-goal tradeoff to a herd owner.

The English summary is being prepared. Showing the original description.

Before designing, training, or auditing ANY model that replicates human-annotated labels, audit the annotation protocol's INPUT — the exact document/evidence the human labelers consulted — and give the model that same input. Use when: (1) designing a classifier/LLM extractor whose target is a hand-coded label set, (2) a label-replication model shows low recall concentrated in a label subset and the diagnosis on offer is "the label's information is not in the features", (3) reviewers propose construct splits (e.g. "designation vs record-evident"), adjudication sittings, or per-domain stop rules to explain residual disagreement with gold, (4) validating an extraction pipeline against labels transcribed from a source document. Symptom of the underlying failure: elaborate theory accumulates to explain why gold is "partially unpredictable" when the model was simply never shown the document the annotators read.

The English summary is being prepared. Showing the original description.

Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

The English summary is being prepared. Showing the original description.

Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and preservation proof.

The English summary is being prepared. Showing the original description.

Manages Google Analytics account and property settings, enables the Analytics Admin API via the Cloud CLI, lists accounts and properties, and manages data streams, custom dimensions, conversion events, and integrations. Use when you need to programmatically configure Google Analytics accounts, provision properties, manage data retention, configure Measurement Protocol secrets, or manage Firebase and Google Ads links.

The English summary is being prepared. Showing the original description.

Generates Google Cloud Monitoring Server-Driven UI (SDUI) Widget and XyChart Protocol Buffer textprotos from resolved PromQL or ListTimeSeries queries. Use when: - Generating valid google.monitoring.dashboard.v1.Widget textprotos, containing PrometheusQuery or TimeSeriesFilter datasets, for use with the Cloud Monitoring Dashboards API, gcloud CLI, or declarative dashboard definitions. - Synthesizing Server-Driven UI (SDUI) widget titles, axis labels, and plot types for Prometheus or ListTimeSeries queries. Don't use for: - Metric discovery or PromQL query generation. For those tasks, use the cloud-monitoring-metric-selection or cloud-monitoring-promql-query skills.

The English summary is being prepared. Showing the original description.

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

The English summary is being prepared. Showing the original description.

Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.

The English summary is being prepared. Showing the original description.

Build native Linux packages (.deb / .rpm / .apk / .pkg.tar.zst) from a PKGBUILD or yap.json project using the yap-mcp Model Context Protocol server. Use this skill whenever the user asks to "build a package", "make a deb/rpm", "cross-compile for arm64/aarch64", "sign a release", generate SBOMs, install a built artifact, or diagnose why a yap build failed. The yap MCP server exposes async builds with buildID polling, validation, dependency-graph inspection, and artifact discovery.

The English summary is being prepared. Showing the original description.

Distinguish the six real reasons a Salesforce query can 'fail', and the protocol for diagnosing before declaring: object doesn't exist, not queryable in edition, permission-denied, field-level errors, namespace prefix missing, API version mismatch. NOT for one object's own query restrictions, required filters or row caps - use apex/soql-object-limits-and-restrictions. NOT for a query that works but is slow - use data/soql-query-optimization.

The English summary is being prepared. Showing the original description.

Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

The English summary is being prepared. Showing the original description.

Detect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol. Auto-detects Makefile targets, package.json scripts, Go tools, Python tools, and other common linters. Use when fixing linting errors, running validation pipelines, or ensuring code quality before committing.

The English summary is being prepared. Showing the original description.

ไกด์มืออาชีพ — itinerary 1-7 วัน, storytelling สถานที่, group dynamics, safety + emergency protocol สำหรับทัวร์ไทย

The English summary is being prepared. Showing the original description.

Blockchain/Web3 Developer — smart contract (Solidity/Rust), ERC-20/721/1155, DeFi protocol, security audit เบื้องต้น, deploy testnet/mainnet

The English summary is being prepared. Showing the original description.

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

The English summary is being prepared. Showing the original description.

Bulletproof agent operating protocol. 15 failure-prevention rules distilled from 120+ real sessions and 10 agent definitions. Covers fabrication, constraint tracking, verification, scoping, retry discipline, and communication. Load before any task to prevent the most common agent failure modes.

The English summary is being prepared. Showing the original description.

Expert in spiritualist practices, séance protocols, mediumship traditions, and historical spiritualism movements from 19th century to modern practices

The English summary is being prepared. Showing the original description.

Expert in Japanese business communication covering keigo, email etiquette, meeting protocols, and corporate culture nuances

The English summary is being prepared. Showing the original description.