Results for “complete”

Structures biological experiments so inference is valid by construction, covering Fisher's principles (randomization, replication, local control), the experimental-vs-observational unit distinction and pseudoreplication (Hurlbert 1984; Lazic 2018), randomization mechanics (complete, restricted, stratified, rerandomization, run-order), blocking layouts (randomized complete block, Latin square, incomplete block), factorial designs and interactions, and the split-plot/nested error strata hidden inside multi-batch genomics. Use when deciding the experimental unit and what counts as a replicate, planning randomization and run order, choosing a blocked/factorial/split-plot/nested layout, avoiding pseudoreplication in cell-culture or animal studies, or specifying the random-effects structure of the analysis model. For assigning samples to sequencing batches/lanes/plates and batch-effect correction see experimental-design/batch-design; for regulated clinical-trial randomization see clinical-biostatistics.

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

Structures biological experiments so inference is valid by construction, covering Fisher's principles (randomization, replication, local control), the experimental-vs-observational unit distinction and pseudoreplication (Hurlbert 1984; Lazic 2018), randomization mechanics (complete, restricted, stratified, rerandomization, run-order), blocking layouts (randomized complete block, Latin square, incomplete block), factorial designs and interactions, and the split-plot/nested error strata hidden inside multi-batch genomics. Use when deciding the experimental unit and what counts as a replicate, planning randomization and run order, choosing a blocked/factorial/split-plot/nested layout, avoiding pseudoreplication in cell-culture or animal studies, or specifying the random-effects structure of the analysis model. For assigning samples to sequencing batches/lanes/plates and batch-effect correction see experimental-design/batch-design; for regulated clinical-trial randomization see clinical-biostatistics.

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

Audit and refresh OpenClaw maturity scorecards using feature definitions, recorded scores, and QA evidence. Review quality, workflow completeness, and long-term support status, then validate source data and regenerate public documentation.

• Review maturity scores for a feature area
• Assess whether expected user workflows are complete
• Update scorecard documentation from QA evidence

Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.

• Checking results before reporting completion
• Confirming that a bug fix resolves the original problem
• Verifying work before a commit or pull request

Implement work described in a specification or tickets, checking types and running tests along the way. Review the completed changes with the code-review skill, then commit the implementation to the current branch.

• Implementing a feature from a specification
• Implementing a referenced issue tracker ticket
• Checking changes with types and tests

Check whether machine learning training is available for a completed Itô GPU booking. Training is currently unavailable; the skill explains this limitation and documents the requirements for a future confirmed handoff of a training plan.

• Checking training availability after a GPU booking
• Reviewing future fine-tuning handoff requirements
• Identifying booking, budget, and confirmation requirements

Generate complete songs locally from lyrics and tags describing mood, instruments, or genre. The skill guides setup, input formatting, memory-saving settings, and MP3 output using the open-source HeartMuLa music models.

• Turn original lyrics into a complete song
• Try different moods and instruments with tags
• Generate music locally or offline

Review a week's calendar, tasks, and notes to identify completed commitments, overdue work, stalled projects, and follow-ups. Turn those findings into a realistic next-week plan that accounts for scheduled commitments and available capacity.

• Review completed commitments and overdue work
• Find stalled projects without a clear next action
• Organize waiting items and follow-up dates

Manage Apple Reminders through remindctl to add, review, edit, and complete personal tasks. Set due dates and separate notification times, organize lists, and sync reminders to Apple devices through iCloud.

• Create personal tasks that sync to iPhone
• Review today's tasks and overdue reminders
• Set a notification before a task's due time

Verify that existing work meets its acceptance conditions using the smallest sufficient set of checks. Reuse results that still match the repository state, report outcomes precisely, and stop once the evidence is complete without adding unrelated work.

• Checking completed work against acceptance conditions
• Running focused checks for specific requirements
• Reusing verification results that remain current

Coordinate a complete Paperclip release, from candidate verification and canary testing to stable npm publication and GitHub Release creation. Track release notes, Docker smoke tests, announcement follow-up, and linked content cases when Cases are enabled.

• Coordinating a complete Paperclip release
• Promoting a tested canary to a stable release
• Checking release candidates with Docker smoke tests

Prepare completed changes for a GitHub pull request with organized commits, a clear title and description, verification evidence, screenshots for interface changes, and explicit replies to review comments through merge readiness.

• Preparing completed changes for a GitHub pull request
• Documenting verification and interface changes
• Replying to review comments and submitting fixes

Run a project's configured build and test commands, including type checks that detect inconsistent data types. Save pass or fail results, failure details, and logs so an automated editing loop can decide whether verification is complete.

• Verifying code after a framework migration
• Checking completed edits for build and test failures
• Using test results to stop an automated editing loop

Format completed work in Grok Bot's claude-mem workflow as searchable XML records with a title, facts, file paths, and narrative. Return a skip marker for idle or initialization states, or when no tool results exist.

• Recording completed work as searchable observations
• Distinguishing idle states from work worth recording
• Standardizing output for the claude-mem generator loop

Control visible local apps and external browser windows through Orca, including clicks, typing, menus, dialogs, and screenshots. Use it for tasks that require interacting with a screen and cannot be completed through commands or APIs.

• Entering text and clicking controls in a local app
• Handling menus and dialogs in an external browser
• Capturing screenshots of a visible window

Review Home Assistant migration behavior for input validation, configuration preservation, and output that does not overwrite existing files. Check storage schema versions, keep secrets out of diagnostics, and identify incomplete automation or integration behavior.

• Reviewing supported storage schema versions
• Checking preservation of unfamiliar configuration fields
• Reviewing writes that must not overwrite existing files

Organize an AI team's work into small tasks with one owner and one deliverable each. Record dependencies, check for duplicate tasks, and update progress so the team's recorded task state stays clear.

• Breaking team work into tasks with clear deliverables
• Assigning owners and recording task dependencies
• Recording blocked work and its reasons

Audit account settings, privacy pages, and API routes for a complete data deletion flow. Check browser storage cleanup, server deletion requests, and user confirmation, then identify missing pieces and guide implementation.

• Audit account deletion flows
• Check browser storage cleanup
• Review server deletion requests

Finalize an implemented OpenSpec change by checking planning files, task completion, and specification differences. Review whether to merge specification updates, verify any requested merge, then archive the change and report its location and outstanding warnings.

• Archiving an implemented change
• Reviewing specification updates before archiving
• Checking unfinished work before closing a change

Archive several OpenSpec changes together after reviewing their documents and task progress. The skill checks code to resolve overlapping specification updates, syncs the selected updates, and reports which changes were archived, skipped, or failed.

• Archive several completed changes together
• Resolve overlapping specification updates
• Review unfinished work before archiving

Implement pending tasks from an OpenSpec change using its specifications and design documents. The skill updates task checkboxes, confirms progress, supports resuming unfinished work, and pauses when requirements or implementation issues need clarification.

• Start implementing a planned OpenSpec change
• Resume partially completed implementation
• Track completed and remaining tasks

Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.

• Record tasks and commitments with deadlines
• Track pending replies and reasons work cannot proceed
• Update task dependencies when prerequisites are completed

Prepare a local browser app or standalone browser file for handoff. Verify its start behavior where supported, then provide exact commands and a reachable URL, or the artifact path, with an honest account of what was checked.

• Hand off a local browser app with verified start instructions
• Deliver a single-file app with a basic startup check
• Share a playable browser game with clear access instructions

Publish a saved Muse Idea or turn a completed activity into reusable instructions. The skill prepares a title, summary, and explanation, removes sensitive details, and returns a link for authenticated Muse users.

• Share a saved Muse Idea
• Turn completed work into reusable instructions
• Publish a generalized workflow without private details