Loading...
Loading...
Found 234 Skills
Analyze meeting notes to find action items and create Jira tasks for assigned work. When Claude needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.
Input contracted creators with their required vs. actual post counts and receive a compliance table with status classifications and escalation notes for non-compliant creators. This skill should be used when checking which creators have fulfilled their posting obligations, auditing deliverable completion across a campaign, tracking contracted vs. actual posts for an influencer program, identifying which creators are behind on deliverables, building a compliance report for campaign creators, flagging overdue or missing creator posts, reviewing posting status across all creators in a campaign, generating escalation notes for non-compliant influencers, or producing a deliverable tracker for a creator campaign. For checking whether a specific piece of content matches the brief requirements, see content-to-brief-compliance-checker. For chasing a specific creator about a late deliverable, see universal-creator-follow-up-chaser. For building a full campaign report with ROI metrics, see campaign-roi-calculator.
Route creator discovery requests into the right collection strategy before platform execution. Use this when the user wants to find creators, KOLs, KOCs, influencers, or partnership candidates and the request includes constraints such as follower range, niche, audience, geography, language, or collaboration fit. This skill decides whether to use handle-first, content-first, graph-first, or mixed discovery, then hands off to TikTok, Instagram, X, and creator-outreach skills.
Use when the user wants Facebook research or workflow guidance for lead generation, influencer discovery, brand monitoring, competitor analysis, content analytics, trend research, or audience analysis, including page or profile audits, post, reel, photo, or comment extraction, group monitoring, transcript retrieval, and Facebook ad or advertiser analysis.
Real-time generation of Xiaohongshu low-follower high-engagement note rankings, filtering high-quality cases with <5000 followers and >500 engagements, allowing content creators and brands to seize the viral content secrets that haven't been overshadowed by top influencers in advance.
Analyze a creator negotiation scenario and generate strategic response options with trade-off analysis and suggested language. This skill should be used when a creator counters with a higher rate, an influencer pushes back on deliverables, a negotiation stalls and you need to re-engage, a creator objects to exclusivity or usage rights terms, you need help responding to a creator's counter-offer, figuring out what to say when a creator asks for more money, handling a creator who wants fewer deliverables, drafting a response to a stalled creator deal, navigating a tricky influencer negotiation, or deciding whether to accept or counter a creator's rate. For estimating fair rates before negotiating, see creator-rate-estimator. For writing initial outreach messages, see creator-outreach-sequence-generator. For classifying a batch of creator replies, see reply-triage-classifier.
Apply Cialdini's six principles of persuasion — Reciprocity, Commitment/Consistency, Social Proof, Liking, Authority, and Scarcity — to analyze or design influence strategies. Use this skill when the user needs to make messaging more persuasive, analyze why a campaign works or doesn't, design sales or marketing copy, or understand social influence tactics — even if they say 'how do we convince people', 'why is this ad effective', or 'make this more persuasive'.
Use this skill to publish markdown documents with mermaid diagrams to directly Confluence.
Aspire platform help — word-of-mouth commerce for influencer marketing, product seeding, affiliate tracking, UGC sourcing, and paid social. Covers Discovery (170M+ profiles, Quickmatch AI, image recognition), Campaign Management (lifecycle tracking, content approval, term sheets), Product Seeding (Shopify gifting, shipping), Affiliate Tracking (promo codes, attribution), UGC & Content (library, repurposing for ads), Paid Social (TikTok Spark Ads, Meta whitelisting), Creator Payments (free processing). Integrates with Shopify, WooCommerce, Meta, TikTok, Pinterest, Klaviyo, CJ, Impact, ShareASale/Awin. Use when Aspire discovery isn't surfacing the right creators, product seeding orders aren't syncing with Shopify, affiliate tracking isn't attributing sales, content approvals are bottlenecked, not sure which Aspire plan fits, or integrations aren't connecting properly. Do NOT use for influencer strategy across platforms (use /sales-influencer-marketing) or affiliate program design (use /sales-affiliate-program).
LaunchDay platform help — curated 24-hour product launch events for indie makers by Dagobert Renouf. Covers $99 submission process (pay only if selected), event model (1-2/month, max 20 products), deal requirements (>40% discount), 30-min podcast interview, influencer promotion (100K+ followers), Slack community access, and permanent archive. Use when unsure if LaunchDay is worth the $99, want more exposure for your indie product but free directories aren't enough, or wondering how LaunchDay compares to other paid options. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt launches (use /product-hunt-launch).
Use when the user wants Instagram research or workflow guidance for lead generation, influencer discovery, brand monitoring, competitor analysis, content analytics, trend research, or audience analysis, including profile analysis, feed collection, post or reel inspection, transcript extraction, comment analysis, reel discovery, highlight retrieval, or embed generation.
Ship a change via a feature branch and pull request — never directly to the default branch. Use after any code change, fix, refactor, or docs update that needs to land on main. Branches are named `<card-number>` from the FluentBoards card. Commits go through the husky pre-commit hook (lint-staged); pushes go to the feature branch only; the PR body links back to the card. Hard refuses any push to main / master / trunk.