Loading...
Loading...
Found 1,060 Skills
Create and refine OpenCode agents via guided Q&A. Use proactively for agent creation, performance improvement, or configuration design. Examples: - user: "Create an agent for code reviews" → ask about scope, permissions, tools, model preferences, generate AGENTS.md frontmatter - user: "My agent ignores context" → analyze description clarity, allowed-tools, permissions, suggest improvements - user: "Add a database expert agent" → gather requirements, set convex-database-expert in subagent_type, configure permissions - user: "Make my agent faster" → suggest smaller models, reduce allowed-tools, tighten permissions
Generate or update PROJECT_MAP.md for user-specified folders. Applicable to scenarios where users request directory maps/project maps/repository overviews/folder-level descriptions/updating existing PROJECT_MAP.md. Must first ask for the folder scope to scan, default full-repository scanning is prohibited; supports single directory or multiple directories (combined or generated separately).
Example skill template. Replace this description with keywords and triggers for your actual skill. This description determines when the skill auto-loads based on conversation context.
Upload and publish videos to YouTube with title, description, tags, thumbnail and subtitles. Use for: youtube upload, publish video, share on youtube.
Turn any concept, idea, or description into a polished static HTML visual, then export it as a PNG or SVG image. Use this skill whenever the user wants to create a visual representation of an idea and needs an image file output (PNG or SVG). This includes: infographics, concept diagrams, flowcharts, comparison charts, process visuals, educational diagrams, social media graphics, data visualizations, posters, cards, badges, icons, logos sketches, or any "make me an image of X" request that can be achieved with HTML/CSS/SVG rather than photographic AI generation. Also trigger when the user has an existing HTML visual and wants to export/convert it to PNG or SVG. Trigger phrases include: "create an image of", "make a visual", "design a graphic", "export as PNG", "save as SVG", "concept to image", "turn this into an image", "screenshot this HTML", "generate an infographic", or any request combining a concept description with image output.
When the user wants to use GitHub for SEO, parasite SEO, GEO, or create curated lists. Also use when the user mentions "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "repository name," "About section," "GitHub description," "GitHub topics," "GitHub Pages," "GitHub gist," "curated list," or "navigation list."
Generate drawio format graphic files based on natural language descriptions. Supports common graphics such as flowcharts, cards, charts, icons, and architecture diagrams. The output is a .drawio file that can be directly opened and edited in drawio. Triggered when the user mentions drawio, drawing, flowchart, architecture diagram, or structure diagram.
Creates a draft GitHub Issue with triage label from natural language description.
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media preview", "my click rate is low", "title optimization", or any meta tag task.
Refresh golden values from a GitHub Actions workflow run (failing-only or all jobs), score the change with average normalized relative differences, and produce a PR-ready summary. Use when the user asks to update goldens for a CI run, refresh golden values from a workflow ID, or generate a golden-value diff summary for a PR description.
Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test-result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports — without inventing facts. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Not for: general prose, blog, or marketing-copy cleanup — use the global humanizer skill. Not for: classifying or routing CI failures — use ai-bug-triage. Related: ai-bug-triage, qa-metrics, qa-dashboard, quality-postmortem.
Analyze a task specification, review the codebase, and output a detailed assessment and success criteria. Use when user provides a new ticket or description to understand scope, risks, and definition of done before implementation.