<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Skills on Vibe Coding</title><link>https://vibecoding.rest/skills/</link><description>Recent content in Skills on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/skills/index.xml" rel="self" type="application/rss+xml"/><item><title>PDF</title><link>https://vibecoding.rest/skills/pdf/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/pdf/</guid><description>&lt;p&gt;The PDF skill packages the specific know-how needed to work with PDFs reliably: filling form fields, extracting text and tables, merging or splitting documents, and generating new PDFs from scratch — using the right libraries and avoiding common formatting pitfalls.&lt;/p&gt;</description></item><item><title>DOCX</title><link>https://vibecoding.rest/skills/docx/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/docx/</guid><description>&lt;p&gt;The DOCX skill covers creating and editing Microsoft Word documents programmatically — headings, styles, tables, tracked changes — in a way that produces files that open correctly in Word rather than malformed XML.&lt;/p&gt;</description></item><item><title>PPTX</title><link>https://vibecoding.rest/skills/pptx/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/pptx/</guid><description>&lt;p&gt;The PPTX skill packages the conventions needed to generate and edit PowerPoint presentations: slide layouts, text formatting, speaker notes, and basic chart or image placement, producing files that open cleanly in PowerPoint or Keynote.&lt;/p&gt;</description></item><item><title>XLSX</title><link>https://vibecoding.rest/skills/xlsx/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/xlsx/</guid><description>&lt;p&gt;The XLSX skill covers working with Excel files properly: writing real formulas rather than pre-computed values, applying number formats and styles, and managing multiple sheets and references correctly.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;It&amp;rsquo;s easy for an agent to produce a spreadsheet that looks right but is actually just static values pasted where formulas should be — which breaks the moment the underlying data changes. This skill steers toward spreadsheets that behave the way a human analyst would build them.&lt;/p&gt;</description></item><item><title>Canvas Design</title><link>https://vibecoding.rest/skills/canvas-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/canvas-design/</guid><description>&lt;p&gt;The Canvas Design skill packages visual design judgment: spacing systems, typographic hierarchy, color restraint, and layout composition — the kind of taste that&amp;rsquo;s easy to describe but hard to consistently apply prompt by prompt.&lt;/p&gt;</description></item><item><title>Brand Guidelines</title><link>https://vibecoding.rest/skills/brand-guidelines/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/brand-guidelines/</guid><description>&lt;p&gt;The Brand Guidelines skill encodes a specific brand&amp;rsquo;s rules — color palette, typography, tone of voice, logo usage — so an agent&amp;rsquo;s output stays consistent with that identity across many separate requests.&lt;/p&gt;</description></item><item><title>Artifacts Builder</title><link>https://vibecoding.rest/skills/artifacts-builder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/artifacts-builder/</guid><description>&lt;p&gt;The Artifacts Builder skill covers the conventions for producing standalone, self-contained interactive outputs — inlined styles and scripts, responsive layout, no external dependencies that would break in a sandboxed viewer.&lt;/p&gt;</description></item><item><title>Webapp Testing</title><link>https://vibecoding.rest/skills/webapp-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/webapp-testing/</guid><description>&lt;p&gt;The Webapp Testing skill packages a verification workflow: launching a dev server, driving a browser through the golden path and edge cases, and checking console and network output for errors — rather than declaring a UI change complete after just reading the code.&lt;/p&gt;</description></item><item><title>MCP Builder</title><link>https://vibecoding.rest/skills/mcp-builder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/mcp-builder/</guid><description>&lt;p&gt;The MCP Builder skill packages the boilerplate and conventions for writing a new &lt;a href="https://vibecoding.rest/mcp-servers/"&gt;MCP server&lt;/a&gt; — the protocol handshake, tool and resource definitions, and error handling patterns that a well-behaved server needs.&lt;/p&gt;</description></item><item><title>Algorithmic Art</title><link>https://vibecoding.rest/skills/algorithmic-art/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/algorithmic-art/</guid><description>&lt;p&gt;The Algorithmic Art skill packages a two-step process for computational art: first drafting a short &amp;ldquo;algorithmic philosophy&amp;rdquo; — a named aesthetic movement with its own manifesto — then expressing that philosophy as a p5.js sketch using noise fields, particles, and seeded randomness. It outputs a philosophy doc, an interactive HTML viewer, and the generative JS itself.&lt;/p&gt;</description></item><item><title>Claude API</title><link>https://vibecoding.rest/skills/claude-api/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/claude-api/</guid><description>&lt;p&gt;The Claude API skill is a language-aware reference for the Anthropic SDK and Messages API — model selection, adaptive thinking, streaming, prompt caching, token counting, and tool/MCP integration — with explicit guidance to verify API shapes against live docs rather than a model&amp;rsquo;s memorized training data.&lt;/p&gt;</description></item><item><title>Doc Co-Authoring</title><link>https://vibecoding.rest/skills/doc-coauthoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/doc-coauthoring/</guid><description>&lt;p&gt;Doc Co-Authoring packages a structured process for writing technical specs, PRDs, decision docs, and proposals: gathering context up front, iteratively building sections through brainstorming and editing, then stress-testing the draft by having a fresh, context-free Claude read it as a real reader would.&lt;/p&gt;</description></item><item><title>Frontend Design</title><link>https://vibecoding.rest/skills/frontend-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/frontend-design/</guid><description>&lt;p&gt;The Frontend Design skill packages a design-lead mindset for building web UI: pin down the subject and its audience, build a compact token system — palette, type pairing, layout concept, one signature element — then critique that plan against known AI-generic defaults before writing any code.&lt;/p&gt;</description></item><item><title>Internal Comms</title><link>https://vibecoding.rest/skills/internal-comms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/internal-comms/</guid><description>&lt;p&gt;Internal Comms packages format- and tone-specific guidelines for recurring internal writing tasks — progress/plans/problems updates, company newsletters, FAQ answers, leadership updates, and incident reports — loading the matching template based on which type of communication is requested.&lt;/p&gt;</description></item><item><title>Skill Creator</title><link>https://vibecoding.rest/skills/skill-creator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/skill-creator/</guid><description>&lt;p&gt;Skill Creator packages the full lifecycle of authoring an Agent Skill: drafting the skill, writing test prompts, running evaluations with variance analysis, reviewing results, and rewriting the skill based on feedback, then optimizing the skill&amp;rsquo;s description for more reliable triggering.&lt;/p&gt;</description></item><item><title>Slack GIF Creator</title><link>https://vibecoding.rest/skills/slack-gif-creator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/slack-gif-creator/</guid><description>&lt;p&gt;Slack GIF Creator packages Slack&amp;rsquo;s specific GIF constraints — 128×128 for emoji, 480×480 for messages, 10–30fps, 48–128 colors, sub-3-second emoji duration — along with a frame-building workflow and validation tools, so requests like &amp;ldquo;make a GIF of X doing Y for Slack&amp;rdquo; produce a file that actually fits Slack&amp;rsquo;s limits.&lt;/p&gt;</description></item><item><title>Theme Factory</title><link>https://vibecoding.rest/skills/theme-factory/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/theme-factory/</guid><description>&lt;p&gt;Theme Factory packages a set of curated color-palette-and-font-pairing themes — Ocean Depths, Sunset Boulevard, Modern Minimalist, and others — shown via a visual showcase, that can be applied to slide decks, documents, or HTML artifacts, or used as a starting point for generating a new theme on the fly.&lt;/p&gt;</description></item><item><title>Superpowers</title><link>https://vibecoding.rest/skills/superpowers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/superpowers/</guid><description>&lt;p&gt;Superpowers packages a battle-tested library of 20+ Claude Code skills — test-driven development, systematic debugging, brainstorming techniques, git worktree management, and root-cause tracing — installable in one shot as a plugin marketplace.&lt;/p&gt;</description></item><item><title>Superpowers Lab</title><link>https://vibecoding.rest/skills/superpowers-lab/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/superpowers-lab/</guid><description>&lt;p&gt;Superpowers Lab is the experimental proving ground for &lt;a href="https://vibecoding.rest/skills/superpowers/"&gt;Superpowers&lt;/a&gt; — newer, less-settled techniques that graduate into the stable library once they hold up in real use.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Skill development benefits from the same staging discipline as software releases — trying new techniques in a lab environment before committing them to a widely-installed stable marketplace avoids regressions for everyone else.&lt;/p&gt;</description></item><item><title>Playwright Browser Automation</title><link>https://vibecoding.rest/skills/playwright-claude/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/playwright-claude/</guid><description>&lt;p&gt;This skill gives Claude Code direct, model-invoked control of Playwright — driving a real browser through a web app&amp;rsquo;s flows to click, fill forms, and validate behavior end-to-end.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Reading component code doesn&amp;rsquo;t confirm a flow actually works in a browser. A dedicated Playwright skill turns that verification into a repeatable, invokable step instead of an ad hoc script written from scratch each time.&lt;/p&gt;</description></item><item><title>iOS Simulator</title><link>https://vibecoding.rest/skills/ios-simulator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/ios-simulator/</guid><description>&lt;p&gt;The iOS Simulator skill lets Claude drive Apple&amp;rsquo;s Simulator directly — building the app, navigating its screens, and exercising flows the way a developer would during manual QA.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;iOS development often has no equivalent to a browser&amp;rsquo;s headless test runner conveniently available mid-conversation. This skill closes that gap by giving Claude a controllable simulator instead of relying on the developer to manually verify every change.&lt;/p&gt;</description></item><item><title>FFUF Web Fuzzing</title><link>https://vibecoding.rest/skills/ffuf-web-fuzzing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/ffuf-web-fuzzing/</guid><description>&lt;p&gt;This skill integrates the ffuf web fuzzer, letting Claude run authenticated fuzzing scans, auto-calibrate for noisy responses, and analyze results for real vulnerabilities during a penetration test.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Fuzzing tools have enough flags and calibration nuance that getting authenticated, low-noise scans right by hand takes real fuzzer expertise. Packaging that expertise as a skill makes competent fuzzing runs repeatable for anyone using it.&lt;/p&gt;</description></item><item><title>Threat Hunting with Sigma Rules</title><link>https://vibecoding.rest/skills/threat-hunting-sigma/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/threat-hunting-sigma/</guid><description>&lt;p&gt;This skill uses Sigma detection rules — a vendor-neutral format for describing log-based threat signatures — to hunt for suspicious activity and analyze security events.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Sigma&amp;rsquo;s rule format is expressive but verbose to write and match by hand across large event logs. A skill that already knows the format turns threat hunting into a repeatable query task instead of a manual log-reading exercise.&lt;/p&gt;</description></item><item><title>Trail of Bits Security Skills</title><link>https://vibecoding.rest/skills/trail-of-bits-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/trail-of-bits-security/</guid><description>&lt;p&gt;Trail of Bits&amp;rsquo; security skills bring their own audit tooling — static analysis with CodeQL and Semgrep, variant analysis, and vulnerability pattern detection — into Claude Code.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Security auditing firms encode years of hard-won pattern knowledge into their tooling configs. Packaging that as a skill means Claude Code inherits Trail of Bits&amp;rsquo; actual audit methodology instead of a generic security pass.&lt;/p&gt;</description></item><item><title>D3.js Visualization</title><link>https://vibecoding.rest/skills/d3js-visualization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/d3js-visualization/</guid><description>&lt;p&gt;This skill teaches Claude to build D3.js charts and interactive data visualizations, handling D3&amp;rsquo;s verbose selection-and-binding API on the model&amp;rsquo;s behalf.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;D3&amp;rsquo;s power comes with a steep, idiosyncratic API that&amp;rsquo;s easy to get subtly wrong. A skill that already knows D3&amp;rsquo;s conventions produces working visualizations faster than re-deriving the pattern from documentation each time.&lt;/p&gt;</description></item><item><title>CSV Data Summarizer</title><link>https://vibecoding.rest/skills/csv-data-summarizer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/csv-data-summarizer/</guid><description>&lt;p&gt;The CSV Data Summarizer skill automatically profiles a CSV file and produces insights with visualizations, without needing a detailed prompt describing what to look for.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Most CSV exploration starts with the same handful of questions — distributions, outliers, missing data, obvious correlations. Automating that first pass saves the back-and-forth of asking for it column by column.&lt;/p&gt;</description></item><item><title>Claude Scientific Skills</title><link>https://vibecoding.rest/skills/claude-scientific-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/claude-scientific-skills/</guid><description>&lt;p&gt;This is a collection of ready-to-use skills for working with specialized scientific libraries and databases, packaging domain knowledge that&amp;rsquo;s otherwise scattered across niche documentation.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Scientific computing libraries often have small, specialist user bases and thin documentation. Bundling working knowledge of them as skills saves re-deriving usage patterns from source code or sparse docs each time.&lt;/p&gt;</description></item><item><title>Recursive Research</title><link>https://vibecoding.rest/skills/recursive-research/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/recursive-research/</guid><description>&lt;p&gt;Recursive Research runs PhD-level research across any domain — tiering sources by reliability and checkpointing findings to disk so long research sessions survive context compaction.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Deep research spanning many sources tends to lose earlier findings once a conversation compacts. Checkpointing to disk mid-research means a long investigation doesn&amp;rsquo;t have to restart from scratch after compaction.&lt;/p&gt;</description></item><item><title>NotebookLM Integration</title><link>https://vibecoding.rest/skills/notebooklm-integration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/notebooklm-integration/</guid><description>&lt;p&gt;This skill lets Claude Code chat directly with Google NotebookLM, grounding answers in a specific set of uploaded source documents rather than general knowledge.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;NotebookLM&amp;rsquo;s source-grounding is useful precisely because it won&amp;rsquo;t answer beyond what&amp;rsquo;s in the uploaded documents. Wiring that into Claude Code keeps document-grounded research and general coding work in the same session.&lt;/p&gt;</description></item><item><title>Markdown to EPUB Converter</title><link>https://vibecoding.rest/skills/markdown-to-epub/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/markdown-to-epub/</guid><description>&lt;p&gt;This skill converts markdown documents and chat summaries into properly formatted EPUB ebook files, handling the packaging EPUB readers expect.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;EPUB is a zipped bundle of XHTML, metadata, and a manifest — not something you get right by hand-writing markup. A skill that knows the format&amp;rsquo;s requirements produces a file that actually opens cleanly in e-readers.&lt;/p&gt;</description></item><item><title>Master Claude for Legal</title><link>https://vibecoding.rest/skills/master-claude-for-legal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/master-claude-for-legal/</guid><description>&lt;p&gt;This skill pack equips Claude for legal-team work — NDA triage, multi-party contract version diffing, citation verification, and meeting briefs — with reference docs on privilege and long-document review baked in.&lt;/p&gt;</description></item><item><title>AWS Skills</title><link>https://vibecoding.rest/skills/aws-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/aws-skills/</guid><description>&lt;p&gt;AWS Skills brings AWS-specific development practice into Claude Code — CDK patterns, cost optimization guidance, and serverless/event-driven architecture conventions.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;AWS has enough service-specific gotchas and cost traps that generic cloud advice often misses them. A skill scoped specifically to AWS and CDK keeps recommendations grounded in what actually works on that platform.&lt;/p&gt;</description></item><item><title>Expo Skills</title><link>https://vibecoding.rest/skills/expo-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/expo-skills/</guid><description>&lt;p&gt;Expo Skills is the official skill set from the Expo team for building React Native apps with Expo, covering the framework&amp;rsquo;s specific conventions and tooling.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Being maintained by the Expo team itself means the skill tracks the framework&amp;rsquo;s actual conventions and release changes, rather than a third party&amp;rsquo;s best guess at Expo&amp;rsquo;s current best practices.&lt;/p&gt;</description></item><item><title>shadcn/ui Skill</title><link>https://vibecoding.rest/skills/shadcn-ui-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/shadcn-ui-skill/</guid><description>&lt;p&gt;The shadcn/ui skill gives Claude Code direct context on shadcn/ui&amp;rsquo;s components and enforces consistent usage patterns across a project.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;shadcn/ui ships as copyable component source rather than an installed package, so consistency depends on the model actually knowing each component&amp;rsquo;s intended API. A skill scoped to shadcn/ui keeps generated UI code matching the library&amp;rsquo;s real patterns instead of guessing.&lt;/p&gt;</description></item><item><title>Get Shit Done</title><link>https://vibecoding.rest/skills/get-shit-done/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/get-shit-done/</guid><description>&lt;p&gt;Get Shit Done is a lightweight meta-prompting and context-engineering system for Claude Code, built around spec-driven development rather than ad hoc prompting.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Spec-first workflows tend to produce more predictable output than freeform prompting, especially on larger features. Packaging that discipline as a skill makes it the default instead of something re-explained per task.&lt;/p&gt;</description></item><item><title>Skill Seekers</title><link>https://vibecoding.rest/skills/skill-seekers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/skill-seekers/</guid><description>&lt;p&gt;Skill Seekers automatically converts any documentation website into a ready-to-use Claude skill, turning scattered docs into structured, invokable reference material.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Most third-party libraries have documentation but no packaged skill. Automating the conversion means any well-documented tool can get a working skill without hand-authoring one from scratch.&lt;/p&gt;</description></item><item><title>Chrome Relay</title><link>https://vibecoding.rest/skills/chrome-relay/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/chrome-relay/</guid><description>&lt;p&gt;Chrome Relay drives the user&amp;rsquo;s already-signed-in Chrome session — cookies, SSO, localhost included — through a local CLI bridge, as a real-browser counterpart to headless Playwright automation.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Some flows only work correctly inside an authenticated, already-logged-in browser session — SSO-gated internal tools, for instance. Relaying through the real Chrome session sidesteps re-authenticating a separate automated browser.&lt;/p&gt;</description></item><item><title>Full-Page Screenshot</title><link>https://vibecoding.rest/skills/full-page-screenshot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/full-page-screenshot/</guid><description>&lt;p&gt;This skill captures full-page screenshots of web pages via the Chrome DevTools Protocol, with zero external dependencies.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Full-page capture (beyond the visible viewport) usually needs either a heavier automation framework or manual scrolling-and-stitching. Talking to the DevTools Protocol directly gets a clean full-page image without either.&lt;/p&gt;</description></item><item><title>n8n Skills</title><link>https://vibecoding.rest/skills/n8n-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/n8n-skills/</guid><description>&lt;p&gt;n8n Skills lets Claude directly understand and operate n8n automation workflows — reading, editing, and reasoning about workflow graphs rather than treating them as opaque JSON.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;n8n workflows are graphs of connected nodes that are awkward to reason about as raw exported JSON. A skill that understands the workflow model can edit and debug workflows the way a human building them in the n8n UI would.&lt;/p&gt;</description></item><item><title>PICT Test Case Design</title><link>https://vibecoding.rest/skills/pict-test-case-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/pict-test-case-design/</guid><description>&lt;p&gt;This skill designs comprehensive pairwise-combinatorial test suites from requirements or code, using Microsoft&amp;rsquo;s PICT methodology to keep the case count manageable.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Testing every combination of inputs is usually infeasible, but pairwise coverage catches most real-world combinatorial bugs with far fewer cases. PICT&amp;rsquo;s methodology is the standard way to generate that reduced set correctly.&lt;/p&gt;</description></item><item><title>Web Asset Generator</title><link>https://vibecoding.rest/skills/web-asset-generator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/web-asset-generator/</guid><description>&lt;p&gt;The Web Asset Generator skill produces web assets like favicons, app icons, and social media images in the sizes and formats each platform actually expects.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Every platform — favicons, Open Graph images, app store icons — has its own required dimensions and formats, which is tedious to track by hand. A skill that already knows those specs saves re-exporting assets that come out the wrong size.&lt;/p&gt;</description></item><item><title>anydesign</title><link>https://vibecoding.rest/skills/anydesign/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/anydesign/</guid><description>&lt;p&gt;anydesign analyzes any image, URL, or Figma file and produces a structured design.md capturing the full design system and component inventory, portable to other AI builders.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Design systems usually live implicitly in a Figma file or an existing site rather than as a portable spec. Extracting that into a structured document means the design system can travel with the project instead of staying locked in one tool.&lt;/p&gt;</description></item><item><title>Frontend Slides</title><link>https://vibecoding.rest/skills/frontend-slides/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/frontend-slides/</guid><description>&lt;p&gt;Frontend Slides creates animation-rich HTML presentations from scratch, or converts an existing PowerPoint deck into one.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;HTML/CSS presentations can do things static slide decks can&amp;rsquo;t — real animation, interactivity, embedded live content — but building one from scratch is its own frontend project. This skill packages that so the format doesn&amp;rsquo;t have to be reinvented per deck.&lt;/p&gt;</description></item><item><title>Loki Mode</title><link>https://vibecoding.rest/skills/loki-mode/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/loki-mode/</guid><description>&lt;p&gt;Loki Mode orchestrates dozens of coordinated AI agents to build, deploy, and operate a complete startup end-to-end, from a PRD through to a live, revenue-generating product.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Coordinating many agents toward one large goal needs explicit role division and hand-off structure, or the agents duplicate work or conflict. This skill packages that orchestration pattern rather than leaving it to be improvised per project.&lt;/p&gt;</description></item><item><title>Rampstack Brand Build Skills</title><link>https://vibecoding.rest/skills/rampstack-brand-build/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/rampstack-brand-build/</guid><description>&lt;p&gt;This 59-skill library covers a website&amp;rsquo;s full lifecycle — brand, design, content, SEO, development, ops, and growth — including a dedicated SEO audit suite.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Building and running a marketing site touches many disciplines that don&amp;rsquo;t usually live in one toolkit. Bundling them together keeps brand, content, and technical SEO work consistent instead of drifting apart across separate tools.&lt;/p&gt;</description></item><item><title>Solo Skills</title><link>https://vibecoding.rest/skills/solo-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/solo-skills/</guid><description>&lt;p&gt;Solo Skills packages seven bilingual (English/Chinese) skills for solo founders and indie developers — launch tweets, customer emails, decision frameworks, and postmortems.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Solo founders repeat the same small set of communication and decision tasks — announcing a launch, writing a postmortem — often enough that having them as ready skills beats rewriting the format each time.&lt;/p&gt;</description></item><item><title>Google Workspace Skills</title><link>https://vibecoding.rest/skills/google-workspace-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/google-workspace-skills/</guid><description>&lt;p&gt;This is a suite of Google Workspace integration skills covering Gmail, Calendar, Chat, Docs, Sheets, Slides, and Drive, with cross-platform OAuth handling.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Each Workspace API has its own auth flow and quirks; wiring up OAuth correctly per app is easy to get wrong. A packaged skill suite means that setup work is done once rather than per integration.&lt;/p&gt;</description></item><item><title>Postgres Query Skill</title><link>https://vibecoding.rest/skills/postgres-query-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/postgres-query-skill/</guid><description>&lt;p&gt;This skill executes safe, read-only SQL queries against PostgreSQL databases, with multi-connection support and defense-in-depth safeguards against destructive statements.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Letting a model run arbitrary SQL against a real database is risky without hard guardrails. Restricting the skill to read-only queries with explicit safeguards makes database exploration usable without risking accidental writes.&lt;/p&gt;</description></item><item><title>Jules Delegate</title><link>https://vibecoding.rest/skills/jules-delegate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/jules-delegate/</guid><description>&lt;p&gt;Jules Delegate hands off coding tasks to Google&amp;rsquo;s Jules AI agent for async work — bug fixes, docs, and tests — directly on a GitHub repo.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Some tasks are better run asynchronously in the background than synchronously in the current session. This skill packages the hand-off so Claude Code can delegate rather than block on work another agent can do independently.&lt;/p&gt;</description></item><item><title>Outline Wiki Skill</title><link>https://vibecoding.rest/skills/outline-wiki-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/outline-wiki-skill/</guid><description>&lt;p&gt;The Outline Wiki skill searches, reads, creates, and manages documents in an Outline wiki instance, whether cloud-hosted or self-hosted.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Team knowledge often lives in a wiki rather than the codebase, so a coding-only agent misses it. Wiring in direct wiki access keeps documentation work and code work in the same conversation.&lt;/p&gt;</description></item><item><title>Deep Research (Gemini)</title><link>https://vibecoding.rest/skills/deep-research-gemini/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/deep-research-gemini/</guid><description>&lt;p&gt;This skill hands off research tasks to Google&amp;rsquo;s Gemini Deep Research agent for autonomous multi-step work — market analysis, competitive landscaping, and literature reviews.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Deep, multi-step research benefits from a purpose-built research agent rather than a general coding assistant improvising a research plan. Delegating to Gemini&amp;rsquo;s dedicated research agent gets a more thorough pass on that kind of task.&lt;/p&gt;</description></item><item><title>Mercury MCP Cheatsheet</title><link>https://vibecoding.rest/skills/mercury-mcp-cheatsheet/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/mercury-mcp-cheatsheet/</guid><description>&lt;p&gt;This reference skill covers the Mercury (Proton) MCP tools for messaging agent teammates, managing threads, and scheduling automations across a coordinated team of agents.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Multi-agent coordination tools tend to have enough surface area — threading, scheduling, teammate addressing — that a quick reference beats re-deriving the API each time. This skill keeps that reference on hand.&lt;/p&gt;</description></item><item><title>Agent Skills Open Standard</title><link>https://vibecoding.rest/skills/agent-skills-open-standard/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/agent-skills-open-standard/</guid><description>&lt;p&gt;Agent Skills is the open SKILL.md standard for packaging reusable agent capabilities — originated by Anthropic and now adopted across Codex, Gemini CLI, Grok Build, Cursor, GitHub Copilot, and more.&lt;/p&gt;</description></item><item><title>Codex Skills System</title><link>https://vibecoding.rest/skills/codex-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/codex-skills-system/</guid><description>&lt;p&gt;OpenAI Codex&amp;rsquo;s built-in skills system discovers SKILL.md skills from &lt;code&gt;~/.codex/skills/&lt;/code&gt; and installs new ones via &lt;code&gt;$skill-installer&lt;/code&gt;, either from OpenAI&amp;rsquo;s curated catalog or any GitHub repo.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Having a first-party install path and curated catalog, rather than only community-assembled lists, is what makes a skills ecosystem practical to actually adopt inside Codex.&lt;/p&gt;</description></item><item><title>OpenAI Skills/Plugins Catalog</title><link>https://vibecoding.rest/skills/openai-plugins-catalog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/openai-plugins-catalog/</guid><description>&lt;p&gt;This is OpenAI&amp;rsquo;s official, curated repository of Codex skills and plugins — covering design tools, testing, security, observability, and one-command cloud deploys.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;A first-party curated catalog is a stronger trust signal than an assembled community list — these skills are maintained by, or reviewed by, OpenAI itself rather than crowdsourced without a review bar.&lt;/p&gt;</description></item><item><title>Figma Design-to-Code Skill</title><link>https://vibecoding.rest/skills/figma-use-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/figma-use-skill/</guid><description>&lt;p&gt;This curated Codex skill bundle wires up Figma — Code Connect, Create Design System Rules, and Generate Design — so Codex can work directly from real design files.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Turning a Figma file into accurate code depends on knowing Figma&amp;rsquo;s specific APIs, like Code Connect and design tokens, rather than guessing from a screenshot. Packaging that as a skill keeps the translation accurate.&lt;/p&gt;</description></item><item><title>Playwright Testing Skill</title><link>https://vibecoding.rest/skills/playwright-codex/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/playwright-codex/</guid><description>&lt;p&gt;OpenAI&amp;rsquo;s curated Playwright skill gives Codex the same browser-automation and interactive test-authoring capability as its Claude Code counterpart, packaged for Codex&amp;rsquo;s skill system.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Verifying a web app in a real browser matters regardless of which coding agent is driving the session — this is the Codex-native equivalent of that same verification step.&lt;/p&gt;</description></item><item><title>GitHub PR Review Skill</title><link>https://vibecoding.rest/skills/gh-address-comments/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/gh-address-comments/</guid><description>&lt;p&gt;This curated Codex skill reads a GitHub pull request&amp;rsquo;s review comments and drives the corresponding fixes back into the branch.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Addressing review feedback is a mechanical loop — read a comment, make the matching change, reply — that&amp;rsquo;s a good fit for automation once the skill knows how to map comments to specific diffs.&lt;/p&gt;</description></item><item><title>CI Fix Skill</title><link>https://vibecoding.rest/skills/gh-fix-ci/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/gh-fix-ci/</guid><description>&lt;p&gt;This curated Codex skill diagnoses and fixes failing GitHub Actions CI runs directly from the failure logs.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;CI failures are usually diagnosable from the log output alone, but pulling and parsing that log by hand is tedious. A skill that already knows how to fetch and read Actions logs shortens the loop from red CI to a fix.&lt;/p&gt;</description></item><item><title>Security Best Practices Skill</title><link>https://vibecoding.rest/skills/security-best-practices-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/security-best-practices-skill/</guid><description>&lt;p&gt;This curated Codex skill applies a secure-coding checklist during code generation and review, catching common vulnerability classes as code is written.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Security issues are cheaper to prevent during generation than to catch in a later review pass. Baking a checklist into the generation step catches classes of bugs before they&amp;rsquo;re ever committed.&lt;/p&gt;</description></item><item><title>Security Threat Model Skill</title><link>https://vibecoding.rest/skills/security-threat-model-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/security-threat-model-skill/</guid><description>&lt;p&gt;This curated Codex skill walks through producing a structured threat model for a system — assets, trust boundaries, and attack surfaces — rather than an ad hoc security discussion.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Threat modeling is only useful if it&amp;rsquo;s structured and complete; an unstructured conversation tends to miss entire categories of risk. A skill that enforces the methodology produces a threat model that&amp;rsquo;s actually useful to a security reviewer.&lt;/p&gt;</description></item><item><title>Sentry Triage Skill</title><link>https://vibecoding.rest/skills/sentry-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/sentry-skill/</guid><description>&lt;p&gt;This curated Codex skill pulls and triages error reports directly from Sentry, connecting production error data to the code that&amp;rsquo;s causing it.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Triaging errors well means correlating a stack trace with the actual code path and recent changes — something that&amp;rsquo;s faster with direct Sentry access than copy-pasting error reports into a prompt.&lt;/p&gt;</description></item><item><title>Jupyter Notebook Skill</title><link>https://vibecoding.rest/skills/jupyter-notebook-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/jupyter-notebook-skill/</guid><description>&lt;p&gt;This curated Codex skill authors and edits Jupyter notebooks programmatically, handling the notebook&amp;rsquo;s cell-and-metadata JSON structure correctly.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Notebook files are structured JSON with execution metadata and outputs, not plain text — editing them without understanding that structure easily corrupts the file. A skill that knows the format keeps notebooks valid while editing.&lt;/p&gt;</description></item><item><title>Notion Spec-to-Implementation Skill</title><link>https://vibecoding.rest/skills/notion-spec-to-implementation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/notion-spec-to-implementation/</guid><description>&lt;p&gt;This curated Codex skill turns a Notion spec document directly into an implementation plan and pull request.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Specs often live in Notion, separate from the codebase, which means implementation work starts with manually re-reading and re-typing the spec. A skill that reads Notion directly removes that translation step.&lt;/p&gt;</description></item><item><title>Cloud Deploy Skills</title><link>https://vibecoding.rest/skills/cloud-deploy-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/cloud-deploy-skills/</guid><description>&lt;p&gt;These curated Codex skills drive one-command deploys to Vercel, Netlify, Render, or Cloudflare directly from the agent, without a separate manual deploy step.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Each platform has its own CLI and deploy conventions; a skill scoped to a specific target means deploys work correctly on the first try instead of trial-and-error against unfamiliar CLI flags.&lt;/p&gt;</description></item><item><title>Skill Creator (OpenAI)</title><link>https://vibecoding.rest/skills/openai-skill-creator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/openai-skill-creator/</guid><description>&lt;p&gt;This system skill, auto-installed with Codex, scaffolds a new SKILL.md-compliant skill from a plain description of what it should do.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Getting a skill&amp;rsquo;s folder structure and frontmatter right by hand is easy to get subtly wrong. A scaffolding skill means authoring a new skill starts from a correct template instead of a blank file.&lt;/p&gt;</description></item><item><title>Google Antigravity Skills System</title><link>https://vibecoding.rest/skills/antigravity-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/antigravity-skills-system/</guid><description>&lt;p&gt;Google Antigravity&amp;rsquo;s skills system supports the same SKILL.md format as Claude Code and Codex, with both global (&lt;code&gt;~/.gemini/config/skills/&lt;/code&gt;) and per-project (&lt;code&gt;.agents/skills/&lt;/code&gt;) scopes.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Supporting the shared SKILL.md format means skills built for Antigravity aren&amp;rsquo;t locked to Google&amp;rsquo;s tooling — the same skill folder is portable to other compatible agents.&lt;/p&gt;</description></item><item><title>Gemini CLI Skills System</title><link>https://vibecoding.rest/skills/gemini-cli-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/gemini-cli-skills-system/</guid><description>&lt;p&gt;Gemini CLI natively supports the Agent Skills (SKILL.md) open standard, letting it load the same skill format used by Claude Code, Codex, and other compatible agents.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;A shared skills format means a skill only has to be written once to work across Gemini CLI and other compatible agents, rather than maintaining separate versions per tool.&lt;/p&gt;</description></item><item><title>Grok Build Skills System</title><link>https://vibecoding.rest/skills/grok-build-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/grok-build-skills-system/</guid><description>&lt;p&gt;Grok Build&amp;rsquo;s skills system reads SKILL.md skills from &lt;code&gt;.grok/skills/&lt;/code&gt;, &lt;code&gt;~/.grok/skills/&lt;/code&gt;, and plugin directories — and is directly Claude Code-compatible, reading &lt;code&gt;.claude/skills&lt;/code&gt; and &lt;code&gt;CLAUDE.md&lt;/code&gt; with zero extra configuration.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Direct compatibility with Claude Code&amp;rsquo;s own skill and config files means a project that&amp;rsquo;s already set up for Claude Code works in Grok Build without any migration step.&lt;/p&gt;</description></item></channel></rss>