<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: BuyAgentSkills</title>
    <description>The latest articles on DEV Community by BuyAgentSkills (buyagentskills).</description>
    <link>https://dev.to/buyagentskills</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F16325%2F1745d97a-4f26-4bed-bf3f-9c855b02c4d1.png</url>
      <title>DEV Community: BuyAgentSkills</title>
      <link>https://dev.to/buyagentskills</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/buyagentskills"/>
    <language>en</language>
    <item>
      <title>SKILL.md Best Practices: Write Skills That Trigger</title>
      <dc:creator>Dishant Singh</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:41:10 +0000</pubDate>
      <link>https://dev.to/buyagentskills/skillmd-best-practices-write-skills-that-trigger-57e8</link>
      <guid>https://dev.to/buyagentskills/skillmd-best-practices-write-skills-that-trigger-57e8</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://buyagentskills.com/guides/skill-md-best-practices/" rel="noopener noreferrer"&gt;buyagentskills.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; A skill works when your agent picks it at the right moment and then follows it. Both depend on the &lt;code&gt;SKILL.md&lt;/code&gt;. Write a description that says what the skill does and when to use it, keep the body short and in the order a person would work, move long reference material into separate files, and test with real prompts.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Written by the Buy Agent Skills team. Updated 17 November 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;New to the format? Start with &lt;a href="https://buyagentskills.com/guides/what-are-agent-skills/" rel="noopener noreferrer"&gt;what are agent skills&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The shape of a skill
&lt;/h2&gt;

&lt;p&gt;A skill is a folder with a &lt;code&gt;SKILL.md&lt;/code&gt; file. At the top is a small frontmatter block with a &lt;code&gt;name&lt;/code&gt; and a &lt;code&gt;description&lt;/code&gt;. Below is the instruction text. Optional files sit beside it, for example &lt;code&gt;references/&lt;/code&gt; for longer notes.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;name: copy-editing
description: Tighten, proofread and review existing marketing copy. Use when the user asks to edit, improve, shorten or check copy for clarity or unproven claims.

&lt;span class="gu"&gt;# Copy editing
&lt;/span&gt;1. Ask for the audience and the goal if they are not given.
2. ...
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;The rules for those two fields&lt;/strong&gt; (from the Agent Skills specification at agentskills.io, read 17 November 2026):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;name&lt;/code&gt;: 1 to 64 characters, lowercase letters, numbers and hyphens only, no hyphen at the start or end, no double hyphens, and the same as the folder name. So &lt;code&gt;copy-editing/SKILL.md&lt;/code&gt; has &lt;code&gt;name: copy-editing&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;description&lt;/code&gt;: 1 to 1024 characters, saying what the skill does and when to use it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Claude Code treats &lt;code&gt;name&lt;/code&gt; as optional and falls back to the folder name, but matching names keep one folder working in every tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Write the description for the agent, not for a catalog
&lt;/h2&gt;

&lt;p&gt;The agent decides whether to use a skill mostly from its &lt;code&gt;description&lt;/code&gt;. Two sentences: what it does, then "Use when ..." with the words a user would actually say.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Weak: &lt;code&gt;Helps with copy.&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Better: &lt;code&gt;Tighten, proofread and review existing marketing copy. Use when the user asks to edit, shorten or check copy for clarity or unproven claims.&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The real &lt;code&gt;copy-editing&lt;/code&gt; skill in our Marketing Copy Pack goes further: its description lists phrases people type, such as "tighten this" and "cut the fluff", and names the sibling skill to use for writing new copy instead.&lt;/p&gt;

&lt;p&gt;If a skill never triggers, the description is the first thing to fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. One skill, one job
&lt;/h2&gt;

&lt;p&gt;A skill that covers pricing, SEO and email will trigger on none of them reliably. Split it. Our packs keep skills narrow, such as &lt;code&gt;pricing&lt;/code&gt;, &lt;code&gt;seo-audit&lt;/code&gt; and &lt;code&gt;signup&lt;/code&gt;, so each description can be specific.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Keep the body short and ordered
&lt;/h2&gt;

&lt;p&gt;Write the steps in the order someone would do the job. Lead with what to ask the user for, then what to produce, then how to check it. The spec recommends keeping &lt;code&gt;SKILL.md&lt;/code&gt; under 500 lines; past that, you are probably carrying reference material that belongs in another file.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Put long reference material in separate files
&lt;/h2&gt;

&lt;p&gt;Keep &lt;code&gt;SKILL.md&lt;/code&gt; as the plan. Link to files in &lt;code&gt;references/&lt;/code&gt; for long checklists, examples and templates, and say when to read them. The agent then loads the extra text only when it is needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Ask for facts, never invent them
&lt;/h2&gt;

&lt;p&gt;Good marketing skills tell the agent to ask for product facts, or read them from a shared context file, and to mark missing numbers as gaps. Our &lt;a href="https://buyagentskills.com/packs/marketing-copy-pack/" rel="noopener noreferrer"&gt;Marketing Copy Pack&lt;/a&gt; does this: claims that need proof are flagged, and missing numbers are left as marked gaps.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Be careful with scripts
&lt;/h2&gt;

&lt;p&gt;If a skill ships scripts, say what each one does and why. Avoid network calls you do not need. Buyers will read them; see &lt;a href="https://buyagentskills.com/guides/how-to-check-an-agent-skill-before-installing/" rel="noopener noreferrer"&gt;how to check a skill before installing&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Keep license notices
&lt;/h2&gt;

&lt;p&gt;If you adapted someone else's skill, keep their license file and credit them. Do not call adapted work original.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Test with real prompts
&lt;/h2&gt;

&lt;p&gt;Write 3 to 5 prompts a user would type, and what a good result contains. Run each in a fresh session and check that the skill loaded and the output matches. Our Marketing Copy Pack ships these as an &lt;code&gt;evals/&lt;/code&gt; folder, so buyers can repeat the check in their own setup. We list what we ran, and what we did not, on each pack page and on &lt;a href="https://buyagentskills.com/how-we-test/" rel="noopener noreferrer"&gt;how we test&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;name&lt;/code&gt; matches the folder name; &lt;code&gt;description&lt;/code&gt; says what it does and "use when"&lt;/li&gt;
&lt;li&gt;One job per skill&lt;/li&gt;
&lt;li&gt;Steps in working order, body short&lt;/li&gt;
&lt;li&gt;Long material in &lt;code&gt;references/&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;No invented facts; gaps marked&lt;/li&gt;
&lt;li&gt;Scripts explained, no needless network calls&lt;/li&gt;
&lt;li&gt;License file kept&lt;/li&gt;
&lt;li&gt;3-5 test prompts run in a fresh session&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Where do skills go?&lt;/strong&gt;&lt;br&gt;
For Claude Code, &lt;code&gt;.claude/skills/&lt;/code&gt;; for Codex, &lt;code&gt;.agents/skills/&lt;/code&gt;. Steps are in &lt;a href="https://buyagentskills.com/guides/how-to-install-skills-claude-code-codex/" rel="noopener noreferrer"&gt;how to install skills in Claude Code and Codex&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My skill never triggers. What now?&lt;/strong&gt;&lt;br&gt;
Rewrite the description with the exact words a user would say, then test again in a new session.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How long should a SKILL.md be?&lt;/strong&gt;&lt;br&gt;
As short as the job allows. Move long material to &lt;code&gt;references/&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need scripts?&lt;/strong&gt;&lt;br&gt;
No. Many useful skills are plain instructions.&lt;/p&gt;

&lt;h2&gt;
  
  
  See it in practice
&lt;/h2&gt;

&lt;p&gt;You can read every &lt;code&gt;SKILL.md&lt;/code&gt; in our packs before you use it. Start with the &lt;a href="https://buyagentskills.com/packs/marketing-copy-pack/" rel="noopener noreferrer"&gt;Marketing Copy Pack ($29)&lt;/a&gt; for three skills and their eval prompts, or the &lt;a href="https://buyagentskills.com/packs/marketing-foundations-pack/" rel="noopener noreferrer"&gt;Marketing Foundations Pack ($39)&lt;/a&gt; for ten.&lt;/p&gt;

&lt;p&gt;Independent product. Not affiliated with or endorsed by Anthropic or OpenAI.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claudecode</category>
      <category>productivity</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Install Agent Skills in Claude Code and Codex</title>
      <dc:creator>Dishant Singh</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:10:16 +0000</pubDate>
      <link>https://dev.to/buyagentskills/how-to-install-agent-skills-in-claude-code-and-codex-4c42</link>
      <guid>https://dev.to/buyagentskills/how-to-install-agent-skills-in-claude-code-and-codex-4c42</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://buyagentskills.com/guides/how-to-install-skills-claude-code-codex/" rel="noopener noreferrer"&gt;buyagentskills.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; A skill is a folder with a &lt;code&gt;SKILL.md&lt;/code&gt; file. To install one, copy the folder into &lt;code&gt;.claude/skills/&lt;/code&gt; for Claude Code or &lt;code&gt;.agents/skills/&lt;/code&gt; for Codex, then start a session and check it loads. Use your home folder (&lt;code&gt;~/.claude/skills/&lt;/code&gt;, &lt;code&gt;~/.agents/skills/&lt;/code&gt;) to make it available in every project.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Written by the Buy Agent Skills team. Updated 17 November 2026. Folders and commands checked against the Claude Code and Codex documentation on 17 November 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;New to the idea? Read &lt;a href="https://buyagentskills.com/guides/what-are-agent-skills/" rel="noopener noreferrer"&gt;what are agent skills&lt;/a&gt; first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Unzip the skill or pack. You should see a folder per skill, each with a &lt;code&gt;SKILL.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Open one &lt;code&gt;SKILL.md&lt;/code&gt; and read it. It is plain text and it tells your agent what to do. See &lt;a href="https://buyagentskills.com/guides/how-to-check-an-agent-skill-before-installing/" rel="noopener noreferrer"&gt;how to check a skill before installing&lt;/a&gt; if it is from someone you do not know.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Claude Code
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;For one project&lt;/strong&gt; (from the project root):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir -p .claude/skills
cp -r path/to/my-skill .claude/skills/my-skill
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;For all projects:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir -p ~/.claude/skills
cp -r path/to/my-skill ~/.claude/skills/my-skill
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Check it loaded:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start Claude Code (or keep your session; edits to existing skills are picked up live).&lt;/li&gt;
&lt;li&gt;Type &lt;code&gt;/&lt;/code&gt; and look for the skill name, or run &lt;code&gt;/skills&lt;/code&gt; for a list.&lt;/li&gt;
&lt;li&gt;If you created the &lt;code&gt;.claude/skills/&lt;/code&gt; folder while a session was already open, run &lt;code&gt;/reload-skills&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Call it with &lt;code&gt;/my-skill&lt;/code&gt;, or ask for a task that matches its description and it should load by itself.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Codex
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;For one project&lt;/strong&gt; (from the repo root):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir -p .agents/skills
cp -r path/to/my-skill .agents/skills/my-skill
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;For all projects:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir -p &lt;span class="s2"&gt;"$HOME/.agents/skills"&lt;/span&gt;
cp -r path/to/my-skill &lt;span class="s2"&gt;"$HOME/.agents/skills/my-skill"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Check it loaded:&lt;/strong&gt; Codex detects new skills automatically. In the CLI, run &lt;code&gt;/skills&lt;/code&gt; or type &lt;code&gt;$&lt;/code&gt; and look for the skill in the list, or run a task that matches its description. If it does not appear, restart Codex.&lt;/p&gt;

&lt;h2&gt;
  
  
  Installing a whole pack
&lt;/h2&gt;

&lt;p&gt;A pack is several skill folders in one zip. Copy each skill folder (not the zip's outer folder) into the skills directory, so each has its own &lt;code&gt;SKILL.md&lt;/code&gt; directly inside. Our packs include a README with the exact steps for that pack.&lt;/p&gt;

&lt;h2&gt;
  
  
  If it does not trigger
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Folder path.&lt;/strong&gt; &lt;code&gt;SKILL.md&lt;/code&gt; must sit directly inside &lt;code&gt;&amp;lt;skills-folder&amp;gt;/&amp;lt;skill-name&amp;gt;/&lt;/code&gt;. One extra folder level is the most common mistake.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Description.&lt;/strong&gt; The agent uses the &lt;code&gt;description&lt;/code&gt; line to decide when to load a skill. If it is vague, call the skill by name or make the description more specific.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Frontmatter.&lt;/strong&gt; The &lt;code&gt;---&lt;/code&gt; blocks at the top must be valid YAML. A stray tab or quote breaks it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Settings.&lt;/strong&gt; In Claude Code, a skill with &lt;code&gt;disable-model-invocation: true&lt;/code&gt; only runs when you call it by name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Restart.&lt;/strong&gt; If Codex does not show a new skill, restart Codex.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Which of our packs work where
&lt;/h2&gt;

&lt;p&gt;Each pack page states what it has been tested in. Check &lt;a href="https://buyagentskills.com/works-with/claude-code/" rel="noopener noreferrer"&gt;works with Claude Code&lt;/a&gt; and &lt;a href="https://buyagentskills.com/works-with/codex/" rel="noopener noreferrer"&gt;works with Codex&lt;/a&gt; before you buy. Today, &lt;a href="https://buyagentskills.com/packs/marketing-foundations-pack/" rel="noopener noreferrer"&gt;Marketing Foundations Pack&lt;/a&gt; and &lt;a href="https://buyagentskills.com/packs/marketing-copy-pack/" rel="noopener noreferrer"&gt;Marketing Copy Pack&lt;/a&gt; are text skills; &lt;a href="https://buyagentskills.com/packs/cartoon-films/" rel="noopener noreferrer"&gt;Cartoon Films&lt;/a&gt; is a larger pipeline that needs macOS on Apple Silicon and Blender and has been tested with Claude Code only. We do not say "works with" until someone has run it. See &lt;a href="https://buyagentskills.com/how-we-test/" rel="noopener noreferrer"&gt;how we test&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need to restart the agent?&lt;/strong&gt;&lt;br&gt;
Claude Code picks up edits to existing skills during a session; use &lt;code&gt;/reload-skills&lt;/code&gt; after creating a new skills folder. Codex detects skill changes automatically; restart it if a change does not appear.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can the same folder serve both tools?&lt;/strong&gt;&lt;br&gt;
Yes, if the skill uses only &lt;code&gt;name&lt;/code&gt; and &lt;code&gt;description&lt;/code&gt;. Copy it to both locations. See &lt;a href="https://buyagentskills.com/guides/codex-vs-claude-code-skills/" rel="noopener noreferrer"&gt;Codex vs Claude Code skills&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Project or personal install?&lt;/strong&gt;&lt;br&gt;
Project install keeps a skill with one repo and lets teammates share it. Personal install makes it available everywhere on your machine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is it safe to install any skill?&lt;/strong&gt;&lt;br&gt;
A skill can tell the agent to run commands. Read it first.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Independent product. Not affiliated with or endorsed by Anthropic or OpenAI.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claudecode</category>
      <category>codex</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Check an Agent Skill Before You Install It</title>
      <dc:creator>Dishant Singh</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:10:15 +0000</pubDate>
      <link>https://dev.to/buyagentskills/how-to-check-an-agent-skill-before-you-install-it-1e9g</link>
      <guid>https://dev.to/buyagentskills/how-to-check-an-agent-skill-before-you-install-it-1e9g</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://buyagentskills.com/guides/how-to-check-an-agent-skill-before-installing/" rel="noopener noreferrer"&gt;buyagentskills.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; A skill is a folder of instructions and sometimes scripts that your AI coding tool will follow. Read it the way you would read a stranger's shell script before running it. Six checks, about ten minutes, no special tools.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Written by the Buy Agent Skills team. Updated 9 November 2026.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why bother
&lt;/h2&gt;

&lt;p&gt;Skills are easy to publish and easy to copy. That is why there are so many good free ones. It also means nobody has necessarily checked the one you found. A skill can tell your agent what to read, what to run and where to send things. If you installed it without reading it, you accepted all of that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The six checks
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Open the folder and list what is in it.
&lt;/h3&gt;

&lt;p&gt;You should see a &lt;code&gt;SKILL.md&lt;/code&gt; and maybe &lt;code&gt;references/&lt;/code&gt; or &lt;code&gt;scripts/&lt;/code&gt;. Surprises are worth a pause: binaries, minified files, or archives you cannot read.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Read &lt;code&gt;SKILL.md&lt;/code&gt; top to bottom.
&lt;/h3&gt;

&lt;p&gt;Look at the description (when will the agent use this?) and the steps. Ask: does every instruction match what the skill says it does? Be careful with lines that say to ignore other instructions, hide output, or act without asking.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Read every script.
&lt;/h3&gt;

&lt;p&gt;In &lt;code&gt;scripts/&lt;/code&gt;, search for these and understand each hit:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl  wget  fetch  http  ssh  scp  nc
rm -rf  sudo  chmod  eval  exec  base64
.env  id_rsa  token  secret  password  API_KEY
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A network call is not automatically bad. A skill that fetches a font may need one. A skill that sends your project files somewhere does not.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Check what it can touch.
&lt;/h3&gt;

&lt;p&gt;Does it write outside the project folder? Read your home directory? Change your shell config or git settings? A skill should need only what its job needs.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Check the license.
&lt;/h3&gt;

&lt;p&gt;Find a &lt;code&gt;LICENSE&lt;/code&gt; file. If there is none, you have no stated right to use or share it. If there is one, check that it allows your use (including commercial use) and keep the notice with the files. Do not strip it.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Test it somewhere safe first.
&lt;/h3&gt;

&lt;p&gt;Install into a scratch project with no secrets and no important files. Run it once. Check what files changed (&lt;code&gt;git status&lt;/code&gt; and &lt;code&gt;git diff&lt;/code&gt; make this easy) before you use it for real work.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick example
&lt;/h2&gt;

&lt;p&gt;Say a skill promises to "clean up my repo". In check 3 you find &lt;code&gt;rm -rf&lt;/code&gt; in a script with a path built from user input. That is not proof of malice, but it is a good reason to read the script closely or choose another skill.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this does not cover
&lt;/h2&gt;

&lt;p&gt;This review catches the obvious problems. It does not prove a skill is perfect or that it will work in every setup. Tools change, so repeat the review when a skill updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you would rather not do this yourself
&lt;/h2&gt;

&lt;p&gt;That is what a tested pack is for. For each pack, Buy Agent Skills checks licenses, reads the scripts, install-tests from a clean folder and publishes what was and was not tested, with dates. See &lt;a href="https://buyagentskills.com/how-we-test/" rel="noopener noreferrer"&gt;How we test&lt;/a&gt;. If a free skill fits and you have reviewed it, use it. Our &lt;a href="https://buyagentskills.com/guides/buy-agent-skills-pack-or-build-your-own/" rel="noopener noreferrer"&gt;buy or build guide&lt;/a&gt; helps you decide.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Are free skills unsafe?&lt;/strong&gt; No. Many are excellent. The point is to read before you run, whoever wrote it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need to read a long SKILL.md line by line?&lt;/strong&gt; Yes for scripts and instructions about files, network and secrets. You can skim background text.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a paid pack remove the need to read?&lt;/strong&gt; Ask what the seller checked, and still skim the files. Reading is cheap.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can an agent do the review for me?&lt;/strong&gt; It can help you spot patterns, but you make the call. Do not let the skill under review judge itself.&lt;/p&gt;

&lt;p&gt;Related: &lt;a href="https://buyagentskills.com/guides/what-are-agent-skills/" rel="noopener noreferrer"&gt;What are agent skills?&lt;/a&gt; | &lt;a href="https://buyagentskills.com/guides/buy-agent-skills-pack-or-build-your-own/" rel="noopener noreferrer"&gt;Buy or build&lt;/a&gt; | &lt;a href="https://buyagentskills.com/packs/" rel="noopener noreferrer"&gt;Browse packs&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Independent product. Not affiliated with or endorsed by Anthropic or OpenAI.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>claudecode</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
