Disclosure: this article has no affiliate links. The skills reviewed here are free and open source under the MIT license. Sophrai is not affiliated with the repository author. Read our affiliate disclosure.
Short answer: you can install Claude Skills in about two minutes. Add the some_claude_skills marketplace to Claude Code and install one skill by name, or copy a skill folder into ~/.claude/skills/. We read the code of the five most useful skills for business teams: an SEO/AI-search auditor, a landing-page appeal scorer, a competitor positioning map, a UX friction audit and an email drafter. They’re useful, with one catch: 104 of the 188 skills pre-approve the Bash tool, so read a skill before you install it. All counts below come from the repo itself, checked on 31 October 2026.
Watch the full walkthrough
More AI agent and automation breakdowns on our YouTube channel: sophraiAI on YouTube.
What are Claude Skills?
A Claude Skill is a folder with a SKILL.md file. The file has a short YAML header (name, description, and optionally allowed-tools), followed by instructions Claude follows when the task matches the description. A skill can also bundle reference documents and scripts. Claude Code loads skills from ~/.claude/skills/ (personal, every project) or .claude/skills/ inside a repo (project only), and picks the right one from its description. You don’t have to call it by name.
For a business team, that means one expert prompt you write once and reuse every time. It follows the same checklist, uses the same scoring template and produces the same output format. A good skill sits somewhere between a saved prompt and a small internal tool.
The some_claude_skills repo in numbers
The collection is maintained by Erich Owens. The repo was at github.com/erichowens/some_claude_skills, and GitHub now redirects it to curiositech/some_claude_skills. We cloned it on 31 October 2026 (latest commit 30 October) and counted ourselves:
| What we checked | Result |
|---|---|
| License | MIT (free to use, modify and ship commercially; keep the notice) |
Skill folders in .claude/skills/ | 188 |
| What the website says | “174+” / “Browse all 174” on someclaudeskills.com (the desktop view says 190+) |
| What the README says | “180+ production-ready skills” |
Skills that pre-approve Bash in allowed-tools | 104 of 188 (55%) |
| Skills that ship script files (.py, .sh, .js, .ts) | 38 of 188 |
| Plugins listed in the marketplace file | 188 (one per skill) |
The three different totals don’t mean much on their own. The catalog grows faster than the docs. But they show why you should check the repo instead of the marketing page, and the same applies to what each skill claims it can do.
How to install Claude Skills in 2 minutes
Option 1: plugin marketplace (fastest)
Inside Claude Code, run:
/plugin marketplace add curiositech/some_claude_skills
/plugin install email-composer@some-claude-skills
Swap email-composer for any skill name. The README also shows a “full collection” command (some-claude-skills@some-claude-skills), but the marketplace file we checked has no plugin with that name. Only individual skills are listed, so install them one by one. That’s the safer choice anyway.
Option 2: manual copy (most control)
git clone https://github.com/curiositech/some_claude_skills.git
mkdir -p ~/.claude/skills
cp -r some_claude_skills/.claude/skills/email-composer ~/.claude/skills/
Copy only the folders you want. The README’s cp -r .../skills/* ~/.claude/skills/ installs all 188 at once, including every skill that pre-approves Bash. To share a skill with your team, copy it into .claude/skills/ in your project repo and commit it. Everyone who opens the repo in Claude Code gets the same skill.
Check that it works
- Restart Claude Code or open a new session.
- Ask in plain words, for example: “Draft a follow-up email to a supplier about a late shipment.”
- Claude should say it is using the skill. If it doesn’t, the description isn’t matching your wording. Mention the skill’s name once.
5 useful Claude Skills for business teams (honest review)
We picked five skills a marketing, growth or ops team can use on day one, and read each SKILL.md, reference file and script. Here is what each one actually does, and what it doesn’t.
| Skill | Best for | Pre-approved tools | Watch out for |
|---|---|---|---|
ultimate-seo-geo-skill | SEO + AI-search (GEO) audits | Read, Write, Edit, Bash, WebSearch | Mentions 24 Python scripts that aren’t in the folder |
product-appeal-analyzer | Landing page and offer review | Read, Write, Edit, WebFetch | Scores are AI judgment, not visitor data |
competitive-cartographer | Competitor positioning map | Read, Write, WebSearch, WebFetch | No market sizing; validator script needs jq |
ux-friction-analyzer | Checkout and onboarding friction | Read, Write, Edit, WebFetch | Simulated users; not an accessibility audit |
email-composer | Customer and supplier emails | Read, Write, Edit | Drafts only; it never sends (good) |
1. ultimate-seo-geo-skill: SEO and AI-search audit
What it does: runs a scored site audit (0–100 Health Score) across 21 modules: technical SEO, Core Web Vitals, on-page, E-E-A-T, schema/JSON-LD, keywords, links, local, hreflang, programmatic SEO, migrations and optimization for AI Overviews, ChatGPT and Perplexity. It has three modes (Audit, Plan, Execute) and two scoring frameworks: CORE-EEAT (80 items) and CITE (40 items).
The catch: the skill says it includes “24 diagnostic Python scripts”. The folder contains only SKILL.md and a plugin manifest, with no scripts. It also pre-approves Bash, so Claude can run shell commands without asking you first while the skill is active. Use it as a structured checklist and prompt, and treat its scores as estimates, not data from a crawler.
Good for: a fast first-pass audit before you open Ahrefs, Semrush or Search Console. It isn’t a replacement for them.
2. product-appeal-analyzer: will people actually want it?
What it does: it’s the “do they want it?” counterpart to friction analysis. It scores a landing page or offer across nine sub-scores in three groups (Identity Fit, Problem Urgency, Trust Signals), for an overall appeal score out of 90. It runs a 5-second test (can a new visitor tell what this is, who it’s for and why it matters within 5 seconds?) and maps objections such as “Is this legit?” and “Too expensive”. It ships a small appeal_scorer.py helper and four reference guides.
The catch: every number is Claude’s judgment from reading your page. None of it comes from heatmaps, analytics or real visitors. It’s useful for spotting weak headlines and missing proof before launch, but check the conclusions with real traffic or an A/B test.
3. competitive-cartographer: a 6-step positioning map
What it does: a 6-step process (define the space → identify direct, adjacent and aspirational players → analyze their positioning → plot a 2D map → find white space → recommend a headline, differentiators and content direction). It pre-approves WebSearch and WebFetch, so it can research competitors’ sites itself.
The catch: the skill says outright that it isn’t for market size estimates or financial forecasts, so don’t expect TAM/SAM numbers. The bundled validate_map.sh needs jq installed. The skill doesn’t pre-approve Bash, so Claude will ask before running the script.
4. ux-friction-analyzer: find where users drop off
What it does: maps a user journey, then runs timed simulations for five personas (Expert, New, Distracted, Explorer, Completer). It scores each friction point (1–10), checks cognitive load and applies Fitts’s Law, Gestalt and ADHD-friendly design principles. The output is a prioritized fix list for checkout, onboarding or signup flows.
The catch: the users are simulated. The skill gives you hypotheses to test, not findings. It also isn’t an accessibility compliance audit (WCAG); the skill itself points you to a separate accessibility-auditor skill for that.
5. email-composer: the safest one to start with
What it does: drafts professional emails, including requests for information, follow-ups, technical updates, customer support replies, meeting requests, polite declines and apologies. It includes tone guides (formal, casual, urgent), subject-line rules and a checklist.
Why it’s the safest: it can only Read, Write and Edit, with no Bash, no web access and no email tools. It never sends anything. You copy the draft and press Send yourself. If you’re new to skills, install this one first.
Security: review Bash permissions before you install
The allowed-tools line in a skill’s header lists the tools Claude may use without asking you while that skill is active. Bash means shell commands: installing packages, deleting files, calling the network, reading your .env. In this repo, 104 of 188 skills (55%) pre-approve Bash and 38 ship scripts. Most of them are probably harmless, but “probably” isn’t good enough on a laptop with client data and API keys.
A 60-second review before you install any third-party skill:
- Open
SKILL.mdand read the header. Ifallowed-toolsincludesBashand the skill doesn’t need it (an email or writing skill doesn’t), removeBashfrom the line. - Read every script in
scripts/. Look forcurl,wget,rm -rf,eval, base64 blobs and access to~/.ssh,.envor credentials. - List the files. If the docs mention files that don’t exist (like the 24 scripts above), the skill may have been edited or copied in a hurry.
- Install only what you use, one skill at a time. Don’t copy all 188 folders.
- Pin a version. For team repos, copy the folder and commit it instead of pulling the latest from someone else’s main branch.
- Keep Claude Code’s permission prompts on for Bash, and run untrusted skills in a dev container or a throwaway VM first.
- Run
grep -l Bash ~/.claude/skills/*/SKILL.mdto list installed skills that mention Bash, then check each one’sallowed-toolsline.
Limitations to know before you rely on Claude Skills
- Judgment, not measurement. The appeal, friction and SEO scores are model opinions. Treat them as a structured second opinion.
- Docs drift. We found three different skill totals (174, 180+, 188) and a skill that describes scripts it doesn’t ship. Check the repo before you trust the docs.
- Claude Code only. These are built for Claude Code. Other agents may read
SKILL.mdfiles, but tool permissions and auto-selection behave differently. - Token cost. Long skills (the UX skill is 421 lines) add context to every run where they trigger.
- No scheduling or integrations. A skill doesn’t run on its own, connect to your CRM or alert anyone. That’s a workflow job (n8n, Make, Zapier).
- Community-maintained. It’s MIT and free, but there’s no SLA. Review changes before you pull updates.
Watch the 60-second version
Verdict: which Claude Skill should you install first?
Start with email-composer: no risk and useful every day. Add product-appeal-analyzer and ux-friction-analyzer before your next landing page or checkout change; together they answer “do they want it?” and “can they use it?”. Use competitive-cartographer once a quarter for positioning. Install ultimate-seo-geo-skill only after you remove Bash from its header or are comfortable approving each command, and don’t expect the 24 scripts it mentions.
Skills give one person a repeatable expert. Workflows give the whole business one. When a skill becomes something your team runs every week, that’s the point to automate it.
FAQ
What are Claude Skills?
Claude Skills are folders with a SKILL.md file that give Claude Code reusable instructions, plus optional reference files and scripts. Claude loads them from ~/.claude/skills/ or a project’s .claude/skills/ folder and uses a skill automatically when your request matches its description.
How do I install Claude Skills?
In Claude Code run /plugin marketplace add curiositech/some_claude_skills, then /plugin install SKILL-NAME@some-claude-skills. Or clone the repo and copy a single skill folder into ~/.claude/skills/. Restart Claude Code and ask a matching question to test it.
Are Claude Skills from GitHub safe?
They can be, but review them first. In the some_claude_skills repo, 104 of 188 skills pre-approve the Bash tool, which lets Claude run shell commands without asking, and 38 ship scripts. Read SKILL.md and any scripts, and remove Bash from allowed-tools if the skill doesn’t need it.
How many skills are in some_claude_skills?
We counted 188 skill folders in .claude/skills/ on 31 October 2026. The website says 174 and the README says 180+. The repo is MIT licensed.
Which Claude Skill is safest to start with?
email-composer. It only has Read, Write and Edit permissions, with no Bash, web access or email tools, so it drafts emails but never sends anything.
Can Claude Skills replace SEO or UX tools?
No. The SEO, appeal and UX friction skills give structured AI judgment and simulated users, not crawler data, analytics or real user testing. Use them for a fast first pass, then confirm with real tools and data.
Sources: curiositech/some_claude_skills on GitHub (cloned 31 October 2026, commit 88a60e3), MIT license, someclaudeskills.com, Claude Code docs. Counts are from our own scan of the skill headers and files. We didn’t benchmark output quality.