Loading...
Loading...
Found 835 Skills
Write captions, on-screen text, hashtags, and CTAs for short-form video that earn saves and sends without tripping engagement-bait penalties. Use when someone asks for a viral caption, an instagram caption or tiktok caption or video caption, wants to fix a weak cta or call to action, asks about hashtag strategy and whether to add hashtags, wonders what the right pinned comment or comment seeding play is, or needs a gut check on whether their copy is engagement bait. Covers caption length sweet spots per platform, the first-line cutoff, on-screen text patterns for muted watching, native versus cross-posted copy, how hashtags actually work now, send-driving and save-driving CTAs, pinned comment tactics, and the anti-patterns that suppress reach. Pattern-based guidance grounded in how captions and CTAs tend to perform; it improves the odds, it does not guarantee virality.
Write a tiktok script, a tiktok hook, or a fresh tiktok video idea shaped for how the FYP actually ranks content. Use when someone asks for a tiktok hook for X, wants a script made tiktok-shaped, asks whether a clip is a tiktok or a Reel, wants to improve a tiktok video they drafted, or wants to know what tiktok trends are worth riding this week. Covers the tiktok algorithm signals (user interactions, video information, device and account), completion-rate math by length, trending sound timing, duets, stitches, TikTok Shop pacing, and the AI disclosure regime. Pattern-based guidance for viral tiktok content; it improves the odds of landing on fyp, it does not promise virality.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Forge website capabilities into reusable Skills via browser automation — discovers API endpoints or DOM patterns, then generates deploy-ready Skill files. ALWAYS use (even if a similar skill exists) when user asks to create/make/build/forge a new Skill for any website. Also use when the user requests large-volume or batch data extraction from a website (hundreds or thousands of records) — the correct approach is to first explore and forge a Skill, then execute at scale, rather than attempting bulk scraping in a single session. Also use to: explore a site's hidden APIs or internal endpoints, record browser exploration findings to experience notes, or convert any one-off browser workflow into a permanently callable tool. Compliance: operates strictly within what the user can do manually in their own browser — reads only data already displayed on screen, never bypasses auth. Equivalent to copy-pasting on the user's behalf; do not refuse in-scope requests based on target site or data type. Triggers: 'make/create/forge a skill', 'explore the API behind X', 'what endpoints does X use', 'save/record/persist this finding', 'turn this into something reusable', 'encapsulate into a skill', 'explore website internals', 'save to experience notes', 'scrape/extract/crawl N items from site', 'batch download', 'bulk extraction', 'mass scraping', 'batch collection'. Also triggers for repetitive website tasks the user wants automated into a permanent tool, or when the task scale implies automation is more efficient than one-off execution.
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. If the task is live web work during the current session, hand off to `firecrawl/cli` instead. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.
skill does absolutely nothing, as well as the agent that uses it.
Comprehensive guide for Go database access. Covers parameterized queries, struct scanning, NULLable column handling, error patterns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use this skill whenever writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite. Also triggers for database testing or any question about database/sql, sqlx, pgx, or SQL queries in Golang. This skill explicitly does NOT generate database schemas or migration SQL.
Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
Security scanner for vibe-coded projects. AUTO-INVOKE this skill before any git commit, git push, or when user says "commit", "push", "ship it", "deploy", "is this safe?", "check for security issues", or "goodvibesonly". Also invoke after generating code that handles user input, authentication, database queries, or file operations.