@paperclipai
Organization
The open-source app everyone uses to manage agents at work
378 skills4 repositories 106.7K
Turn a user request into a Paperclip case with workflow instructions and an initial agent. Start the case, document its workflow with a state diagram and transition explanations, and return links to the case and primary task.
Investigate failed, stalled, slow, or incorrectly blocked Paperclip tasks. Trace the cause, reproduce the bug, implement a repair, test related behavior, and verify the actual workflow before delivering a pull request with passing checks.
Add a new execution tool or provider to native Paperclip Runner. Define requirements, investigate its communication protocol, implement the integration, package it, and verify complete tasks in the intended environment, including cancellation, recovery, and cleanup.
Investigate slow Paperclip runs, page requests, and CI suites using Honeycomb traces, which show timed operations. Find relevant traces, separate overlapping work, identify dominant delays, and configure optional tracing or add missing measurements.
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.
Investigate slow PostgreSQL queries in Paperclip, reproduce their cost locally, and implement measured fixes. Compare performance and returned results, add regression coverage, and carry pull requests through review and automated checks.
Audit a test suite to identify redundant tests, empty checks, and tests tied to internal implementation. Consolidate or remove them with evidence while preserving useful checks that detect regressions, meaning previously fixed problems returning.
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.
Audit a project's verification skill and maps of features and agent access against source code and live behavior. Correct documented procedures and references, while clearly identifying untested operations, access gaps, and missing prerequisites.
Review Paperclip interface changes using Storybook, a catalog of component examples, alongside production source and existing browser tests. Report rendering, interaction, visual comparison, and production evidence separately, making simulated behavior and untested areas clear.
Maintain Paperclip Storybook examples by comparing them with shipped interfaces and the feature map. Update fixtures, classifications, and catalog references while preserving stable links and clearly identifying current examples, prototypes, historical work, and cases needing review.
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.
Generate a project-local skill that launches and operates an app through real user workflows. It documents feature checks, captures evidence, and cleans up created instances, then proves the generated instructions work with one end-to-end run.
Investigate failing or pending checks on the latest commit of a GitHub pull request. Reproduce actionable failures, fix and push changes, then recheck remotely until checks pass or a specific blocker is reported.
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.
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.
Track pull requests opened by a Paperclip instance, explain their purpose, and assess whether their latest changes are ready to merge. Dispatch preparation work for unresolved problems and publish an evidence-based report without merging anything.
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.
Prepare Paperclip changes for a pull request by organizing commits, updating the branch, writing the description, addressing automated review feedback, and checking tests and CI before reporting the result for handoff.
Publish a folder of static HTML and assets to the configured Paperclip S3/CloudFront host. Validate the folder before upload, obtain a persistent public URL, and update an existing page from its original publishing directory.
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.
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.
Produces detailed HTML or Markdown reports on pull requests, branches, or large code contributions. It explains how the system works, ranks concrete findings, compares designs when needed, and recommends whether and how to merge the changes.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)