997 skills · sorted by relevance
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.
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.
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.
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.
Coordinate bounded test runs for one Terminal-Bench task through Paperclip. Record evidence, diagnose failures, and manage approval for product fixes while keeping reruns in the same isolated working copy.
Guide Ramp setup and spending workflows in Paperclip using current official instructions. Account applications, card creation, payments, and financial data sharing require explicit approvals that define the permitted action, amount, and data.
Coordinate agent work through the Paperclip API by checking assignments, updating task status, posting progress, delegating subtasks, and requesting approvals. It records deliverables and dependencies so reviewers and other agents can follow the work and continue it.
Delegate work to an existing Paperclip agent by selecting a suitable assignee and creating a task with clear objectives, constraints, and deliverables. Receive a lasting task reference and check progress after the conversation ends.
Check earlier Paperclip tasks for verified progress and actual deliverables, then report findings with links. When requested, add feedback as the connected person, with safeguards against posting the same comment twice.
Review stalled, blocked, or pending-review issues in Paperclip and choose one concrete next action for each. Clarify ownership and status, then resume work, reassign it, resolve blockers, request a decision, or close the issue.
Turn an authorized plan into Paperclip work by deciding which tasks need separate owners, defining clear deliverables, and recording real dependencies so independent work can start and dependent work waits.
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.
Review a connected Paperclip team's agents, projects, tasks, and pending approvals. Summarize active work, blockers, unavailable agents, and decisions requiring attention, with task references and approval links so the user can inspect the findings.
Guide development of new interaction cards in Paperclip issue threads, such as approvals or structured questions. Covers shared data definitions, server behavior, interface states, CLI and MCP support, plugin helpers, documentation, and tests.
Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.
Create and maintain Paperclip status cards for work you want to track. Turn a plain-language request into focused task searches, produce an initial summary, and update reports using the changes or snapshots supplied to the assigned run.
Set up a Paperclip maintenance bot that applies a chosen skill to a repository and opens pull requests. Configure its agent, schedule or event trigger, work limits, reviewers, and readiness checks before activation.
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.
Verify Paperclip through real browser or command-line journeys across source checkouts, published npm installations, or existing hosted environments. Record the exact version, platform, starting data, observed behavior, and supporting evidence for each tested journey.
Prepare user-facing changelogs for stable Paperclip releases from commits, change records, and merged pull requests. Group related changes, identify breaking changes, and explain upgrade actions using the beta version selected for release.
Turns a stable Paperclip release changelog into a Discord announcement in dotta’s conversational style. It combines shipped highlights with plans grounded in current work and saves a draft for a person to copy and publish.
Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.
Records an agent’s brief, unfiltered complaints about tools, permissions, or working conditions in Paperclip. It preserves the reaction without requiring a diagnosis or solution, then lets the agent continue its main task.
Investigate stalled or repeatedly recovering task trees in Paperclip using task states, run records, and recent changes. Produce an evidence-based cause analysis and a phased product-rule plan for approval, without changing code.