Loading...
Loading...
Found 6,677 Skills
Help non-technical stakeholders write clear, scoped requirements documents. Translates business needs into structured specs including user goals, workflows, and success criteria — but first guides the requester through prioritization, scope limits, and MVP phasing to prevent wishlist bloat. Output in Taiwan Traditional Chinese. Use this skill when your boss, PM, or stakeholder wants to define what a feature should do, write a PRD, plan a product, or describe requirements. It is also suitable when someone presents a large feature wishlist and needs help structuring and narrowing down its scope.
Build, debug, and extend integrations with the EasyPost shipping API. Use this skill whenever the user mentions EasyPost, shipping labels, postage, rate shopping, tracking packages programmatically, customs forms, carrier accounts (USPS/UPS/FedEx/DHL/ePost Global), scan forms, pickups, shipping insurance, or webhooks for shipping events. Also trigger on phrases like "create a shipping label," "buy postage," "rate a parcel," "verify an address," "international shipment," "commercial invoice," "Luma rate shopping," "UPS DAP," "DHL eCommerce," or any task involving the `@easypost/api` Node.js SDK or REST endpoints under `api.easypost.com/v2`. Optimized for Node.js/TypeScript but the REST patterns, field names, and carrier gotchas apply in any language.
When the user wants to optimize truck loading, load delivery vehicles, or plan vehicle capacity utilization. Also use when the user mentions "truck loading," "delivery vehicle optimization," "van loading," "cargo van packing," "multi-drop vehicle loading," "delivery route loading," "axle weight distribution," or "vehicle utilization." For container loading, see container-loading-optimization. For route optimization, see route-optimization.
CrowdPower integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with CrowdPower data.
Authors and consumes feature-level domain knowledge files in ai-context/features/. Reference guide for bounded-context business rules, invariants, integration points, and known gotchas.
Use when deploying a database to Zeabur. Use when user needs MySQL, PostgreSQL, MongoDB, or Redis. Use when user says "I need a database", "add database", "deploy postgres", "set up MySQL", "add Redis", "add MongoDB", or "connect to database". Also use when user mentions data persistence issues like "data lost after restart", "data not saved", "data disappears", "need persistent storage for data", or "how to persist data". Also use when integrating a database with an existing service.
Analyzes and compares existing skills from any source (skills.sh, GitHub, Claude marketplace, or local files) against a target skill or requirement. Fetches skill content, evaluates it across 10 dimensions, produces a structured comparison table, identifies gaps, and recommends whether to adopt, adapt, or build from scratch. Trigger when: analyze this skill, compare skills, is this skill good enough, what does this skill do, skill evaluation, should I use this skill, skill gap analysis, paste a skills.sh URL, GitHub skill URL, or upload a SKILL.md file for review.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.
Monitors email deliverability via Mailgun Optimize (InboxReady) API. Use when the user wants to test inbox placement with seed lists, monitor IP or domain blocklists, track spam traps, check email health scores, review DMARC reports, or pull Google Postmaster or Microsoft SNDS data. Also use when emails are going to spam, sender reputation is dropping, inbox rate is declining, a domain needs warmup monitoring, an IP needs blocklist removal, or the user wants to set up email deliverability monitoring.
Audit a codebase for maintenance and modernization. Challenges scope, reviews architecture/quality/tests/performance/dependencies, files deferred work via bd. Language-specific addendums for iOS/Swift, Go, and Web/JS/CSS activate automatically based on what's in the repo. Supports monorepos with mixed stacks.
imagine is a multi-provider command-line tool for generating and editing images via Google Gemini, Google Vertex AI, and OpenAI (gpt-image-2).
Ultra-lightweight channel for feature workflows: No need to write design docs, checklists, or conduct phased reviews. Let AI write code directly as it normally would, but before it starts, tell it where the CodeStable knowledge base in the project is and how to search it. This way, the code it writes will have fewer pitfalls and be more consistent with project conventions. Trigger scenarios: Users say "fast mode", "fastforward", "skip all those steps", "just start coding", "help me make xxx" and the requirement is too small to go through the design process.