Loading...
Loading...
Found 358 Skills
Find relevant Reddit, HN, and ProductHunt threads and draft value-first community responses with launch checklist. Use when user says "find communities", "draft outreach", "Reddit promotion", "ProductHunt launch", or "community marketing". Do NOT use for social media posts (use /content-gen) or video scripts (use /video-promo).
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.
Use when creating, adding, or modifying plugins in this Glean Claude Plugins marketplace repository. Triggers on "create plugin", "add plugin", "new plugin", "plugin checklist", "marketplace", or when working with plugin.json, marketplace.json, or the plugins/ directory. Ensures all required files are updated correctly.
Takes activated influencers and their deliverables and generates a structured monitoring checklist specifying what to capture on each platform, when to check, and what to do if content goes missing. This skill should be used when building a content monitoring plan for a creator campaign, creating a checklist to track influencer deliverables across platforms, setting up a capture schedule for Instagram Stories before they expire, planning when to screenshot or capture creator posts, building a monitoring cadence for TikTok and YouTube deliverables, organizing content capture across multiple creators and platforms, making sure no creator content slips through the cracks, preparing a content tracking plan before a campaign goes live, or setting up a system to catch expiring Stories and time-sensitive posts. For checking whether submitted content matches the brief, see content-to-brief-compliance-checker. For tracking which creators have posted versus who is overdue, see creator-posting-compliance-tracker.
Takes a campaign brief and submitted creator content description and produces a structured pass/fail checklist against every brief requirement. This skill should be used when checking if creator content matches the brief, reviewing influencer deliverables against requirements, auditing submitted content for brief compliance, verifying a creator hit all the brief requirements, running a content QA check before approval, comparing a draft to the original brief, grading content against campaign specifications, or reviewing creator submissions before giving approval. For converting raw feedback into a polished revision request to send to a creator, see content-approval-feedback-formatter. For FTC disclosure compliance specifically, see ftc-disclosure-spot-checker.
Use when making design decisions, reviewing UI for HIG compliance, choosing colors/backgrounds/typography, or defending design choices - quick decision frameworks and checklists for Apple Human Interface Guidelines
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth (SSOT) for execution checklist and status), and provide an unambiguous task list for subsequent I2 execution.
[Code Quality] Run quality gate checklist. Use for pre-release, pre-dev, or pre-QA quality verification.
Maintain `*-skills` README standards and checklist-style roadmap docs through one canonical maintenance entrypoint. Use when a repo needs profile-aware README maintenance, checklist roadmap validation or migration, or a bounded audit-first doc workflow with Markdown and JSON reporting.
Expert guidance for designing, assessing, and optimizing Azure workloads using Azure Well Architected. Covers design review checklists, recommendations, design principles, tradeoffs, service guides, workload patterns, and assessment questions. Use when designing AI, SAP, Oracle, SaaS, HPC, or mission‑critical workloads on Azure, and other Azure Well Architected related development tasks.
Code review checklist for LobeHub. Use when reviewing PRs, diffs, or code changes. Covers correctness, security, quality, and project-specific patterns.
Mechanize Pattern 15 — the seven-pass adversarial review protocol for academic manuscripts. Spawns 7 forked subagents in parallel (abstract, intro, methods, results, robustness, prose, citations), then synthesizes a prioritized revision checklist. Use for submission-ready or R&R-stage papers where single-pass review isn't enough.