Loading...
Loading...
Found 2,011 Skills
Continuous repository security scanning and release gating. Triggers: "security scan", "security audit", "pre-release security", "run scanners", "check vulnerabilities".
Deep code audit that finds dead wiring, silent failures, unfinished features, placeholder stubs, bloated files, and unnecessary complexity. Produces an actionable report with file:line references grouped by severity. Think of it as a senior dev doing a thorough PR review of the entire codebase. Triggers on: "code review", "audit the code", "review the code", "find dead code", "find placeholders", "check for stubs", "prune the code", "code cleanup", "implementation review", "completeness check", "find unused code".
React Native Reanimated 4.x best practices, 60fps animation patterns, bug fixing, and code enhancement for Android and iOS. Use when writing, reviewing, fixing, or optimizing Reanimated animation code, gesture-driven interactions, worklets, layout animations, or shared element transitions. Triggers on tasks involving react-native-reanimated, useSharedValue, useAnimatedStyle, withSpring, withTiming, withDecay, Gesture.Pan, layout animations, worklet debugging, animation performance optimization, or troubleshooting janky animations. Also use when the user wants to fix animation bugs, enhance animation smoothness, review gesture code, or achieve 60fps on both Android and iOS. Also triggers when the user asks to review, audit, check, or upgrade their Reanimated code to best practices, or asks "is my animation code good", "check my reanimated code", "update to best practices", "review my animations", or similar requests.
Audit and maintain project rules in .cursor/rules/. Use when auditing project rules, checking prefix convention, syncing doc/rules.md, or when the user asks about .cursor/rules or prefix convention.
Analyze an influencer's recent content and return a brand safety report flagging political controversy, offensive language, sensitive topics, or past scandal indicators. This skill should be used when screening a creator for brand safety, vetting influencer content for risks, checking if a creator is brand-safe, auditing an influencer's content history for red flags, running a brand safety check on a creator, evaluating creator risk before a partnership, flagging controversial creator content, reviewing an influencer for offensive language or sensitive topics, or doing a pre-campaign safety review. For holistic creator evaluation including performance metrics, see creator-vetting-scorecard. For writing campaign briefs with content guidelines and safety clauses, see campaign-brief-generator.
Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support.
Version-controlled evolution engine that uses accumulated insight results to evolve soul profiles and workflow recipes with auditability, safety constraints, and rollbacks.
Ghost Security - Software Composition Analysis (SCA) scanner. Scans dependency lockfiles for known vulnerabilities, identifies CVEs, and generates findings with severity levels and remediation guidance. Use when the user asks about dependency vulnerabilities, vulnerable packages, CVE checks, security audits of dependencies, or wants to scan lockfiles like package-lock.json, yarn.lock, go.sum, or Gemfile.lock.
Ghost Security - Secrets and credentials scanner. Scans codebase for leaked API keys, tokens, passwords, and sensitive data. Detects hardcoded secrets and generates findings with severity and remediation guidance. Use when the user asks to check for leaked secrets, scan for credentials, find hardcoded API keys or passwords, detect exposed .env values, or audit code for sensitive data exposure.
Analyzes Java code against industry best practices and evaluates design principles including SOLID, exception handling, thread safety, and resource management. Reviews naming conventions, Stream API usage, Optional patterns, and general code quality. Use when reviewing Java files, checking code quality, evaluating exception handling, or auditing resource management.
Optimize agent skills to reduce context bloat while preserving answer coverage. Use when: (1) A skill's SKILL.md body exceeds ~250 lines or duplicates its references/ files (2) A skill's YAML description is verbose or triggers false positives from sibling skills (3) Planning or executing a body/reference split for a skill (4) Auditing skill token efficiency
Ensures baseline security practices are followed in the project. Use this when asked to perform a security audit on the codebase. Automatically creates Jira stories for each security finding.