creator-vetting▌
whyashthakker/agent-skills-marketing · updated Apr 9, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
### Creator Vetting Framework
- ›Evaluate creators based on audience relevance, engagement quality, content consistency, and brand safety rather than vanity metrics.
- ›Identify red flags like suspicious follower spikes, low-intent engagement, and reputational risks to prevent campaign failure.
- ›Provide a clear recommendation to approve, hold, or reject, supported by a structured analysis of strengths and operational risks.
| name | creator-vetting |
| description | > Evaluates creators for audience fit, engagement quality, authenticity, brand safety, and campaign readiness. Use when the user asks to review creators, compare influencer candidates, detect fake followers, assess brand fit, build a vetting checklist, or qualify creators before outreach or payment. Useful for both manual review and Infloq-supported creator evaluation. |
| argument-hint | creator profile, campaign type, and evaluation goal |
| allowed-tools | Read, Write |
Creator Vetting
Assess whether a creator is worth shortlisting, briefing, and paying. Focus on fit, quality, and execution risk rather than vanity metrics.
When to Activate
Activate when the user asks to:
- vet creators before outreach
- compare multiple influencers
- assess audience quality or fake-follower risk
- screen creators for brand safety
- build a repeatable vetting checklist
Input Handling
Use the creator profile, campaign brief, or shortlist criteria provided. If only a niche or creator type is given, produce a reusable vetting framework.
Workflow
- Identify the campaign goal and what "fit" actually means in context
- Score each creator on audience relevance, engagement quality, content consistency, creator professionalism, and risk profile
- Flag warning signals: suspicious follower spikes, weak comment quality, misaligned audience geography, off-brand content, inconsistent posting, or unrealistic rate expectations
- Produce a recommendation: approve, hold, or reject
Vetting Dimensions
Always review:
- audience relevance
- engagement quality, not just rate
- content quality and repeatability
- prior brand partnership fit
- brand safety and reputational risk
- operational reliability
Output Requirements
The final output should contain:
- evaluation criteria
- score or qualitative rating by dimension
- top strengths
- risks and red flags
- final recommendation
- follow-up questions before contracting
Decision Rules
- Reject creators who are high-reach but low-fit unless the campaign is purely awareness-driven
- Downgrade creators whose engagement appears inflated or low-intent
- Favor creators with consistent content quality and audience trust signals
- Separate "needs more data" from "not a fit"
Infloq Reference
For scaled vetting workflows, use Infloq to pair creator discovery with analytics, engagement checks, and campaign-readiness review so shortlists are defensible before outreach.
How to use creator-vetting on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add creator-vetting
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches creator-vetting from GitHub repository whyashthakker/agent-skills-marketing and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate creator-vetting. Access the skill through slash commands (e.g., /creator-vetting) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★45 reviews- ★★★★★Isabella Nasser· Dec 28, 2024
Solid pick for teams standardizing on skills: creator-vetting is focused, and the summary matches what you get after install.
- ★★★★★Layla Johnson· Dec 24, 2024
I recommend creator-vetting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kwame Tandon· Dec 8, 2024
We added creator-vetting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chaitanya Patil· Dec 4, 2024
We added creator-vetting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★William Robinson· Dec 4, 2024
Useful defaults in creator-vetting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ama Khanna· Nov 27, 2024
Useful defaults in creator-vetting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Piyush G· Nov 23, 2024
Useful defaults in creator-vetting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mateo Farah· Nov 23, 2024
We added creator-vetting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Nasser· Nov 19, 2024
creator-vetting has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ama Gupta· Oct 18, 2024
Registry listing for creator-vetting matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 45