claude-skills is a large collection of reusable skills, commands, plugins, and supporting resources for coding agents across engineering, business, research, compliance, and productivity work. It is used by people who want agents such as Claude Code, Codex, Gemini CLI, or Cursor to follow specialized workflows. The catalogue contains selected skills and settings from the collection.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add alirezarezvani/claude-skills --skill competitive-intelgit clone --depth 1 https://github.com/alirezarezvani/claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/alirezarezvani/claude-skills/competitive-intel)<a href="https://agentmods.dev/skills/alirezarezvani/claude-skills/competitive-intel"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/competitive-intel/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alirezarezvani/claude-skills/competitive-intel"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/competitive-intel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 1 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00066 | $0.01864 |
| Opus 5.5 | $0.00026 | $0.00746 |
| Sonnet 5.5 | $0.00013 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
competitive-intel scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence
Systematic competitor tracking. Not obsession — intelligence that drives real decisions.
Keywords
competitive intelligence, competitor analysis, battlecard, win/loss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy
Quick Start
Ask in natural language for the deliverable you need:
"Map our competitive landscape" — direct, indirect, and future competitors "Build a battlecard for [competitor]" — sales-ready battlecard "Run a win/loss analysis" — recent wins and losses by reason "What did [competitor] do recently?" — competitor update tracking "Build a competitive positioning map" — 2x2 positioning map
Framework: 5-Layer Intelligence System
Layer 1: Competitor Identification
Direct competitors: Same ICP, same problem, comparable solution, similar price point. Indirect competitors: Same budget, different solution (including "do nothing" and "build in-house"). Future competitors: Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.
The 2x2 Threat Matrix:
| Same ICP | Different ICP | |
|---|---|---|
| Same problem | Direct threat | Adjacent (watch) |
| Different problem | Displacement risk | Ignore for now |
Update this quarterly. Who's moved quadrants?
Layer 2: Tracking Dimensions
Track these 8 dimensions per competitor:
| Dimension | Sources | Cadence |
|---|---|---|
| Product moves | Changelog, G2/Capterra reviews, Twitter/LinkedIn | Monthly |
| Pricing changes | Pricing page, sales call intel, customer feedback | Triggered |
| Funding | Crunchbase, TechCrunch, LinkedIn | Triggered |
| Hiring signals | LinkedIn job postings, Indeed | Monthly |
| Partnerships | Press releases, co-marketing | Triggered |
| Customer wins | Case studies, review sites, LinkedIn | Monthly |
| Customer losses | Win/loss interviews, churned accounts | Ongoing |
| Messaging shifts | Homepage, ads (Facebook/Google Ad Library) | Quarterly |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · +203 lines · +66 tokens per session 647c53414f51
- 1mo ago First seen · 1 lines · 0 tokens per session scan A f9021ff86839
competitive-intel is a skill published in the GitHub repository alirezarezvani/claude-skills (28,607 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,864 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…