Skill request

Request a missing Skill

Use this path when the marketplace does not yet have the workflow your team needs, or when an existing skill is close but not exact.

What to send

The best requests describe the business job, not only a tool name.

Workflow category such as growth, e-commerce, data, support, sales, developer QA, or security
Current tools or data sources involved
Input example and the output you expect
How often the team runs this workflow
Permission needs such as network, browser, files, or secrets
Whether it should be free basics, Pro catalog, or future paid-marketplace

Requests are grouped by repeated pain, adoption value, permission risk, and whether the workflow can be made safe and reusable.

Operators first check whether an existing skill already solves most of the job.
Low-risk, broadly useful basics may become free starter skills.
Advanced, recurring, or high-value workflows are usually Pro candidates.
High-risk workflows need clearer owner approval, examples, and runtime boundaries before listing.

Specific requests are easier to turn into a useful skill than broad requests like 'make marketing better'.

Audit Shopify product pages and return title, bullets, trust gaps, and SEO fixes.
Clean a CSV of leads and output normalized company, role, region, and next action.
Review a landing page screenshot and return mobile layout, trust, CTA, and copy issues.

FAQ

No. SkillHub prioritizes repeatable workflows that can be described, governed, reviewed, and maintained.

Yes, but private or customer-specific skills need support ownership, permission scope, and delivery expectations reviewed before commitment.