Loading...
Loading...
Found 984 Skills
The YouTube publish-metadata skill. Use when someone wants to "write a YouTube title/description," "set tags/category/privacy," "optimize YouTube SEO/metadata," set made-for-kids, or publish a YouTube video via WoopSocial. Writes the metadata (title, description+chapters, tags) and sets category/privacy/madeForKids — YouTube is a search engine, so metadata is the launchpad, and madeForKids is a COPPA/FTC legal flag set truthfully. Uses the INDEX framework. Reads brand-profile + goals-and-kpis + the script/video first. The video file + script are inputs (not WoopSocial); the thumbnail and A/B title testing are native YouTube Studio; WoopSocial publishes via the YouTube fields; metrics never fabricated. Distinct from youtube-long-form/youtube-shorts (the script) and thumbnail-design (the thumbnail).
Hunts complexity in the current diff and APPLIES the simplifications directly to the working tree, then verifies the build. Five angles: reuse (duplicate logic, hand-rolled stdlib, platform features), quality (React/TypeScript hygiene, over-memoisation, exhaustive-deps, `any`, `CLAUDE.md`/`AGENTS.md` violations), efficiency (unnecessary work, missed concurrency, hot-path bloat), altitude (bandaid fixes special-cased onto shared code), and test discipline (repro test per bug fix, useless tests deleted, new tests only when they prevent a named failure). Hand it a `pr-reviewer` report and it applies those confirmed findings too. Use when the user says "tidy this up", "simplify", "clean up this diff", "polish my changes", "make this simpler", "apply the review findings", or "any reuse opportunities?". For a read-only report instead, use `pr-reviewer`; for the PR's title, description, or commits, use `pr-creator`.
Generate a complete System Analysis & Design document (use cases, sequence/activity/state diagrams, class + ER model, data dictionary, architecture, screens, traceability) from one validated central model — Markdown canonical, PDF optional. Trigger on /sa-doc, "ทำเอกสาร SA", "เขียนเอกสารวิเคราะห์และออกแบบระบบ", "ทำ project report วิชา SA", "generate SA document", "system analysis document", "SA&D report", "SDD", or when the user hands over a brief/requirements/codebase and asks for a full design document. Do NOT use for a single ad-hoc diagram, for explaining a problem interactively (problem-description), or for reviewing an existing document (scrutinize).
A brief description of what this skill does
Builds targeted B2B prospect lists from Twitter/X profiles and posts using apidojo's Twitter scrapers on Apify. Triggers when the user asks to: find Twitter users with a specific job title or keyword in bio, build a list of founders or executives on Twitter, find people tweeting about a topic for outreach, identify potential customers on X, scrape Twitter profiles matching an ICP description, find decision-makers in a specific industry on Twitter, or export a list of leads from Twitter bios. Returns name, username, bio, follower count, location, and recent tweet samples per prospect. Ideal for B2B SDRs, growth hackers, founder-led sales teams, and partnership managers.
Turn any idea, brief, or rough instruction into 4 ready-to-paste prompts for AI image models (Midjourney, Nano Banana, GPT Images, Seedream, Flux, any other). Use when the user asks for an image prompt, a thumbnail / banner / logo / illustration prompt, says "write a prompt for this image", or wants to turn a description into something an image model can render. Differentiator: writes the prompt text only — to actually generate the image use the deepapi skill.
Read this when writing or revising articles. It applies to explanatory texts such as documentation, comments, commit messages, PR descriptions, and articles, as well as reading material such as novels. It is also useful for fixing prose that feels “AI-like” or is difficult to read.
Generate Dreamina-compatible prompts from music analysis — per-section visual descriptions
Update naming and documentation references across the Claude Pilot codebase. Use when renaming features, updating descriptions, changing terminology, or ensuring consistency after modifying commands, skills, or workflows. Triggers on "update references", "rename X to Y across codebase", "sync documentation", or "update all mentions of X".
Analyze HM Desktop PRD documents, extract requirement information, verify completeness, check chapter order (Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description), inspect KEP definitions, detect requirement conflicts, and generate structured analysis reports. Applicable to user requests: (1) Analyze or review PRD documents, (2) Extract KEP lists from requirements, (3) Check PRD completeness or consistency, (4) Map requirements to module architecture, (5) Verify PRD format compliance, (6) Verify completeness of competitor analysis chapters. Keywords: PRD analysis, requirement extraction, KEP verification, completeness check, chapter order validation, competitor analysis check, analyze PRD, requirement extraction, completeness check, chapter order validation
Complete Product Hunt launch preparation. Generates tagline, description, maker comment, gallery checklist, topics, hunter outreach, launch timeline. Use when: preparing PH launch, writing PH copy, creating launch checklist. Zero external deps - pure content generation. Keywords: product hunt, launch, tagline, maker comment, PH, producthunt.
6 AI personalization prompts (lemlist style) plus 2 email templates - ICP Identification, Company Description, Similar Product, Top 3 Problems, Subject Line, Case Study Reference, and Similar Company Approach. Use when setting up AI-powered personalization, building Clay/lemlist workflows, or automating research.