'cli' 검색 결과

Start and repair isolated Paperclip development workspaces through managed services. Restore a full database clone when needed, then verify login, populated data, health, service visibility, and whether the process using the port belongs to the intended workspace.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting or restarting a managed development workspace
• Repairing setup, login, or missing cloned data
• Resolving port conflicts between workspaces

Prepare and submit requests to add agents in Paperclip. Check hiring permissions, compare existing configurations, and define the role, instructions, reporting line, and runtime settings, then handle approval and follow-up for linked tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Requesting a new agent for a specific role
• Matching a new agent to existing team settings
• Drafting role instructions and runtime settings

Turn bundled Paperclip issues, comments, and documents into readable wiki updates covering project purpose, current progress, decisions, risks, and next actions, while preserving existing knowledge and citing the supporting activity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarizing recent project activity in a wiki
• Building wiki pages from historical project activity
• Recording decisions and their supporting evidence

Find and install command-line tools that let AI agents operate professional software. Search by task or category, check which workflow capabilities are available locally, and install the specific tools needed for a multi-tool project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find command-line tools for image editing or 3D modeling
• Check available tools for a video production workflow
• Install only the capabilities needed for a task

Delegate repository analysis and coding tasks to Antigravity CLI without an interactive session. The skill checks structured results and errors, and supports comparing its work with results from another coding agent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delegate project code analysis to Antigravity CLI
• Request changes to specific files
• Compare results from different coding agents

Guide shell, Python, and Node.js execution on the computer running a connected A0 CLI. It explains session reuse, interactive input, output retrieval, and recovery steps when execution permissions, timeouts, or disconnections interrupt the work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run shell commands on the connected A0 CLI host
• Execute Python or Node.js on the host
• Retrieve output or answer an interactive program

Deploy ClawHub to production or publish a stable CLI release to npm. Check prerequisites for the exact commit, run the release workflow, and verify the deployed behavior or published version with traceable release evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy ClawHub to production
• Publish a stable ClawHub CLI version
• Check release prerequisites for a specific commit

Check harness changes on a host without Docker by running the pinned Claude Code CLI against a local mock API server. Capture request headers and verify behavior using the authentication environment generated by the harness.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check authentication changes without Docker
• Inspect headers sent by the real CLI
• Reproduce the environment passed to container agents

Build a white-labeled, client-facing intelligence dashboard — a live, branded reporting surface an agency stands up per client instead of sending static reports. Covers brand auto-extraction from the client's URL, a three-tier build (Basic/Standard/Advanced), an onboarding feature wizard, a 10-page inventory, public-access tradeoffs, and the retention plays that make the dashboard sticky. Use when "client dashboard", "client intelligence dashboard", "white label dashboard", "client portal", "branded dashboard for my client", "agency dashboard", "build my client a dashboard", "give the client a live view instead of a report", or any request to stand up a durable, client-facing reporting surface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Connect to and query ClickHouse (a local server or a ClickHouse Cloud service) from the terminal. For ClickHouse Cloud analytics, use the configured direct ClickHouse Query API endpoint with per-user CH_API_KEY and CH_API_SECRET credentials; do not use clickhousectl cloud service query. For local or host/port servers, use clickhousectl local client. Use when the user wants to run SQL against ClickHouse, explore schemas and tables, inspect Cloud services, or authenticate. For building a local dev environment or deploying to Cloud, defer to the official ClickHouse skills (see Scope).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sets up a complete per-client workspace in Cowork with isolated context, preferences, deliverable templates, running notes, decision log, and automatic status reporting. For consultants, agencies, and professional services. Useful when onboarding a new client, during engagement kickoffs, for organizing existing client relationships, and when multiple clients need isolated context. Use when the user says "set up a client", "new client project", "client system", "client context", "client workspace", or "onboard a client".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert-level climatology covering climate system components, climate forcing and feedbacks, paleoclimatology, climate modeling, and climate change science.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and test two-way integrations between Paperclip and external bots such as Dot. Cover invitations, identity, permissions, task delivery, recovery, and Cloud deployment, with evidence from real provider accounts and deployed environments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect an external bot for two-way work
• Build invitation and connection setup screens
• Test recovery after restarts or duplicate events

Select, inspect, validate, and report Paperclip evaluations for Runner protocol behavior or complete product workflows. Interpret results with evidence, source revisions, costs, and failure categories, and refresh reports from retained evidence without new provider calls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing between Runner and Product E2E evaluations
• Inspecting evaluation catalogs without credentials
• Interpreting failures using evidence and execution records

Coordinate Paperclip vulnerability response from confidential report review and private fixes to local testing, CVE identifier requests, advisory publication, and immediate security releases, with human assistance for reporter communication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a confidential vulnerability report
• Developing and testing a fix in a private fork
• Coordinating advisory publication and a security release

Research MCP connections, which let agents use external tools, and vendor integrations for Paperclip. Produce an evidence-backed planning pull request, obtain human approval for its exact revision, then implement and verify each approved connection separately.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Researching MCP and vendor connection requirements
• Preparing integration plans for human approval
• Implementing approved Paperclip connections separately

Turn an idea, post, or task into a skill for the Paperclip catalog. Search for existing skills first, then reference, adapt, or author one, add worked examples where applicable, validate the catalog, and prepare a pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn an idea or article into a catalog skill
• Register an existing external skill in the catalog
• Adapt a related skill with source attribution

Build and update Paperclip interfaces using shared rules for colors, typography, status indicators, layouts, and interactions. Reuse existing components and keep the component catalog and showcase page aligned with new or changed interface elements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add pages that follow Paperclip UI conventions
• Create reusable interface components
• Standardize status colors and priority icons

Create, implement, or review Paperclip capsule visuals that represent agents and their status. Apply the rules for each visual type, document settings for reproducible assets, and provide static alternatives for animated effects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create capsule avatars for agents
• Implement heartbeat status indicators
• Prepare hero capsule graphics for marketing

Write or revise a Paperclip plan that states the intended outcome, constraints, approach, and success checks. Capture unresolved decisions, maintain the saved plan, and request approval when the work requires it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a plan with clear outcomes and success checks
• Clarifying uncertainties before starting work
• Updating an existing plan without duplicating it

Tidy a Paperclip Mine inbox by scanning entries and grouping archive candidates by work status and inactivity. Present checkbox confirmations, then archive only accepted selections, with undo details and no changes to the underlying tasks, branches, or workspaces.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clear completed work from a Mine inbox
• Review inbox entries that have been inactive for a long time
• Check stale work that still has unmerged commits

Set up OmniRoute and manage its command-line configuration. Inspect and validate tool settings, manage environment variables, check for updates, and control automatic startup using commands that support both interactive and unattended setup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a provider and default model
• Inspecting and validating CLI tool settings
• Checking or changing environment variables

Configure Codex CLI to connect through OmniRoute on Linux, macOS, or Windows. The workflow detects the operating system and shell, creates configuration files and seven profiles, sets environment variables, and verifies the setup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect Codex CLI to OmniRoute
• Set up Codex across different operating systems
• Create seven named configuration profiles

Prepare and publish standalone @cline/ui releases to npm, the package registry. Covers version updates, quality checks, production and preview channels, release verification, and the initial setup that lets GitHub Actions publish the package.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a production UI package release
• Publishing a preview with an explicit prerelease version
• Checking tests and package contents before release