@paperclipai
Organization
The open-source app everyone uses to manage agents at work
378 skills4 repositories 106.9K
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.
Compare README, specification, and product documents with recent git history to find outdated claims or missing features. Make small factual corrections, preserve the existing style, and prepare a pull request for review.
Manage an AI-agent company in Paperclip through conversation. Set up the company, hire and configure agents, handle approvals, track tasks and spending, and review work products, with summaries and links to the relevant web pages.
Maintain a local company wiki by incorporating source material, answering questions, and organizing navigation. Preserve original sources while keeping citations, links, and update logs, with project summaries that separate current status from lasting knowledge.
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.
Create acceptance criteria and a manual validation plan for feature changes. Cover successful flows, unusual inputs, failures, and performance limits, with observable outcomes and clear evidence requirements so reviewers can decide whether each criterion passes.
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.
Draft simple black-and-white screen layouts as standalone SVG files, with numbered explanations of each area. For multiple screens, create a flow overview and an optional static viewer page for browsing and zooming during review.
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.
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.
Read email linked to assigned Paperclip tasks, send new messages or replies through an assigned AgentMail inbox, and check delivery outcomes. Follow task permissions and preserve retry identifiers to avoid duplicate sends.
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.
Summarize a Paperclip project or workspace in plain language, starting with up to three concrete actions needed to unblock work. Review issues and comments, then save a concise Markdown update to its summary slot.
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.
Review a screen, user flow, or component against the user's task. Assess visual hierarchy, interaction cues, error handling, accessibility, and consistency, then provide prioritized fixes with reasons and identify strengths worth preserving.
Record concrete improvements in Paperclip when an agent encounters significant workflow friction. The skill turns observed problems with tools, permissions, environments, or documentation into brief internal feedback while keeping the main task moving.
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.
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.
Audit an LLM Wiki for conflicting or outdated claims, broken links, missing concept pages, weak sources, and index inconsistencies. Return findings grouped by severity with evidence and suggested fixes, leaving page content unchanged.
Answer questions using Paperclip wiki pages and original sources, with citations for each claim. Identify missing information clearly and, with user approval, save useful comparisons or explanations as linked wiki pages for future reference.
Create and maintain a lightweight weekly editorial calendar based on company priorities. Connect company goals to publishable topics, with owners, status, and verification notes recorded alongside the planned content.
Turn a captured source document into linked LLM Wiki pages for sources, entities, concepts, and combined insights. Update the index and log, preserve the original material, and flag contradictions with existing knowledge instead of silently replacing it.
Review another agent’s recent work records to identify recurring problems and propose small changes to instructions, skills, or tool descriptions. Produce evidence-backed drafts and reviewable diffs, checking that proposed rules would preserve successful outcomes from past tasks.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)