Generates a CSS stylesheet for a lobster.js page, targeting lbs-* class names. Use this whenever the user wants to style a lobster.js page, create a CSS theme for lobster.js, customize the visual appearance of a lobster.js site, or asks for CSS that targets lbs-* classes. Also trigger when a user describes a visual style (e.g. "dark mode", "minimal", "playful") while working on a lobster.js project — even if they don't mention CSS or lbs-* explicitly. --- Generate a CSS stylesheet for a lobster.js page based on the user's design description. lobster.js outputs semantic HTML where every element has a predictable `lbs-*` class name. Write CSS targeting these classes to style the page. Use the design description from the user's message. If no description is given, generate a clean minimal light theme. --- ## HTML structure reference ```html <!-- Content wrapper --> <div id="content"> … </div> <!-- Page regions --> <header class="lbs-header"> … </header> <footer class="lbs-footer"> … </footer> <!-- Headings --> <h1 class="lbs-heading-1"> … </h1> <h2 class="lbs-heading-2"> … </h2> <!-- h3–h6 follow the same pattern --> <!-- Paragraph --> <p class="lbs-paragraph"> … </p> <!-- Inline --> <em class="lbs-emphasis"> … </em> <strong class="lbs-strong"> … </strong> <del class="lbs-strikethrough"> … </del> <code class="lbs-code-span"> … </code> <!-- Horizontal rule --> <hr class="lbs-hr" /> <!-- Code block --> <div class="lbs-code-block"> <div class="lbs-code-filename">filename.js</div> <!-- optional --> <pre data-language="js"><code class="language-js"> … </code></pre> </div> <!-- Blockquote --> <blockquote class="lbs-blockquote"> <p class="lbs-paragraph"> … </p> </blockquote> <!-- Lists --> <ul class="lbs-ul"> <li class="lbs-list-item"> … </li> </ul> <ol class="lbs-ol"> <li class="lbs-list-item"> <input type="checkbox" class="lbs-checkbox" /> … <!-- task list --> </li> </ol> <!-- Table (standard) --> <table class="lbs-table"> <thead><tr><th> … </th></tr></thead> <tbody><tr><
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
Upload archive: .zip / .skill (recommended)
Upload skills folder
Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
Claude Code:~/.claude/skills/
Codex CLI:~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared across tools?
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
Wrong folder path or nested one level too deep
Invalid/incomplete SKILL.md fields or format
Dependencies missing (Python/Node/CLI)
Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills: