GitHub Actions workflow for automated pragmatic code review on pull requests, posting triage-leveled findings as PR comments
Skills in this repository
paperclipai/companies - Page 3
SkillsMP has collected 122 skills from paperclipai/companies. Open a skill to review its source and details.
paperclipai/companiesShowing 40 of 122 collected skills.
GitHub Actions integration for automated design review on pull requests that modify frontend files
Perform a comprehensive 8-phase UI/UX design review covering Preparation, Interaction, Responsiveness, Visual Polish, Accessibility, Robustness, Code Health, and Content across 1440px, 768px, and 375px viewports using Playwright
Perform a 7-tier hierarchical code quality review covering Architecture, Functionality, Security, Maintainability, Testing, Performance, and Dependencies with triage levels (Critical/Blocker, Improvement, Nit)
GitHub Actions workflow for automated security review on pull requests with confidence-gated PR comments
Perform a focused 3-phase security review with vulnerability identification, false-positive filtering, and confidence scoring (>80% exploitability threshold) covering Input Validation, Auth, Crypto, Injection, and Data Exposure
Create new Aeon skills from a description
Analyze codebase health metrics including complexity and dependencies
Track DeFi protocol metrics including TVL, yields, and liquidations
Monitor watched GitHub repos for new activity and changes
Curate and summarize top Hacker News stories
System health check that verifies agent operations are running correctly
Capture and catalog new ideas from conversations and research
Triage and categorize new GitHub issues on watched repos
Prune stale memory entries and consolidate the memory index
Synthesize overnight activity into a daily actionable briefing
Monitor on-chain events like large transfers and contract deployments
Thorough code review for pull requests on watched repositories
Self-reflection on recent activity to identify patterns and improvements
Focused research analysis on a specific topic with sources
Search Semantic Scholar for academic papers on a given topic
Scan security advisories and vulnerability disclosures
Audit skill configurations for correctness and freshness
Monitor token prices and trigger alerts on significant movements
Curate and summarize tweets from tracked accounts and topics
Summarize activity for watched blockchain wallets
Comprehensive weekly review of goals, progress, and recommendations
Multi-agent team orchestration CLI for spawning agents, managing tasks, and coordinating work through mailbox messaging and git worktree isolation
Explores user intent, requirements and design before implementation. Use before any creative work — creating features, building components, adding functionality, or modifying behavior.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable — requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification
Use when starting any conversation — establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always