CRM Icp Analysis
cognyai/claude-code-marketing-skills
Analyze HubSpot CRM data to build a data-driven Ideal Customer Profile from closed-won deals, contacts, and companies
Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library.
Install Icp Deep Scanner
$ npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OneWave-AI/claude-skills icp-deep-scanner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/icp-deep-scanner .claude/skills/icp-deep-scanner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "icp-deep-scanner" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scanner into .claude/skills/icp-deep-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icp-deep-scanner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OneWave-AI/claude-skills icp-deep-scanner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/icp-deep-scanner .agents/skills/icp-deep-scanner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "icp-deep-scanner" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scanner into .agents/skills/icp-deep-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icp-deep-scanner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OneWave-AI/claude-skills icp-deep-scanner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/icp-deep-scanner .cursor/skills/icp-deep-scanner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "icp-deep-scanner" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scanner into .cursor/skills/icp-deep-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icp-deep-scanner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OneWave-AI/claude-skills.git --path icp-deep-scanner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OneWave-AI/claude-skills icp-deep-scanner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/icp-deep-scanner .gemini/skills/icp-deep-scanner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "icp-deep-scanner" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scanner into .gemini/skills/icp-deep-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icp-deep-scanner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OneWave-AI/claude-skills icp-deep-scannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/icp-deep-scanner .github/skills/icp-deep-scanner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "icp-deep-scanner" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scanner into .github/skills/icp-deep-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icp-deep-scanner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OneWave-AI/claude-skills icp-deep-scanner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/icp-deep-scanner .opencode/skills/icp-deep-scanner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "icp-deep-scanner" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/icp-deep-scanner into .opencode/skills/icp-deep-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icp-deep-scanner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
icp-deep-scanner- GitHub stars
- 336
- Token cost
- ~1.8k tokens
- SKILL.md length
- 697 words
- Files
- 1
- Skills in repo
- 69
- Repo updated
- First seen
- Licence
- MIT
At a glance
Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library.
- Works in 5 steps: Inventory connectable sources → Extract signal from each source → Synthesize the ICP → …
- You need to define
- SKILL.md covers Operating principles (read…, Step 1 — Inventory connectable…, Step 2 — Extract signal from… and Step 3 — Synthesize the ICP, plus 3 more sections
- Needs SUPABASE_TOKEN and OPENAI_API_KEY
What it does
Icp Deep Scanner is an agent skill from OneWave-AI/claude-skills. Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library. Read-only by default. Use when you need to define or refresh your ICP, build buyer personas from real data instead of guesses, or generate the persona inputs that the customer-panel-of-experts and prospect-panel-simulator skills consume.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Positioning and messaging and CRM management. The repository describes itself as: 200+ production-ready Claude Code skills for sales, marketing, design, engineering, and AI agent architecture. Built and maintained by OneWave AI. The licence is MIT.
When your agent uses it
- You need to define
- Refresh your ICP
- Build buyer personas from real data instead of guesses
- Generate the persona inputs that the customer-panel-of-experts and prospect-panel-simulator skills consume
Example prompts
- “/icp-deep-scanner”
Requirements
- A credential in SUPABASE_TOKEN
- A credential in OPENAI_API_KEY
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fc5b785. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SUPABASE_TOKENOPENAI_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Icp Deep Scanner loads about 1.8k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 697 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from OneWave-AI/claude-skills at commit fc5b785, republished under its MIT licence (© OneWave-AI). 697 words, ~1,751 tokens.
Download SKILL.mdSave it as
.claude/skills/icp-deep-scanner/SKILL.md (or your agent's skills folder).- name
- icp-deep-scanner
- description
- Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library. Read-only by default. Use when you need to define or refresh your ICP, build buyer personas from real data instead of guesses, or generate the persona inputs that the customer-panel-of-experts and prospect-panel-simulator skills consume.
- tools
- Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, Agent
- model
- inherit
ICP Deep Scanner
Turn the data already sitting in your connected tools into a rigorous, evidence-backed Ideal Customer Profile (ICP) and a library of buyer personas. Most ICPs are invented in a slide deck. This one is reverse-engineered from your actual best customers, your won/lost deals, your support tickets, and your reviews — then written so it can drive real decisions and feed the panel skills.
This skill is the data layer beneath customer-panel-of-experts, prospect-panel-simulator, and product-launch-war-room. Run it first; those skills read the persona library it writes.
Operating principles (read first)
- Read-only by default. You may query and read connected sources. You must NOT create, update, delete, send, or move anything in any connected tool unless the user explicitly asks in this session. Before any write or outbound action, stop and confirm.
- Least data necessary. Pull aggregates and representative samples, not entire databases. You are building a profile, not exfiltrating a CRM.
- PII minimization. Persona artifacts are archetypes, not dossiers. Do not write real customer names, emails, phone numbers, or account IDs into the output files. Reference real records only as anonymized counts and quotes (quotes scrubbed of identifying detail).
- Secrets via environment only. Never read, print, or write credentials. Assume tokens live in environment variables (e.g.
$SUPABASE_TOKEN,$OPENAI_API_KEY) or in the MCP connection itself. If a source needs auth that isn't present, list it under "Sources I could not reach" and continue. - Cite the evidence. Every claim in the ICP must trace to a source. "Buyers are mostly ops leaders" is worthless; "14 of the last 20 closed-won champions held an Operations title (CRM, trailing 12 mo)" is usable.
Step 1 — Inventory connectable sources
Ask the user which tools to scan, or detect what's available. Map each to what it tells you:
| Source (examples) | What to extract | How to reach it |
|---|---|---|
| CRM (HubSpot, Salesforce, internal) | Closed-won vs closed-lost firmographics, titles of champions/buyers, deal size, sales cycle, win reasons | MCP connector or read-only API |
| Email / calendar | Who actually engages, meeting cadence, recurring objection language | Gmail/Calendar MCP, read-only |
| Support / tickets / chat | Top pain themes, words customers use, where they get stuck | Intercom/Zendesk export, logs |
| Reviews (G2, Capterra, Trustpilot, App Store) | Verbatim value language, switching triggers, deal-breakers | WebFetch / customer-review-aggregator |
| Product analytics (GA4, Clarity, Mixpanel) | Activation paths, who sticks, drop-off points | Analytics MCP / API |
| Billing (Stripe, Mercury) | Real revenue concentration, expansion vs churn by segment | Read-only API |
| Database (Supabase/Postgres) | Ground-truth usage and cohort behavior | Read-only SQL via $SUPABASE_TOKEN |
| Public web | Firmographic enrichment, market sizing, competitor positioning | WebSearch / WebFetch |
Present the list, mark which are reachable now, and confirm scope before scanning. For a wide scan across many sources, dispatch parallel read-only sub-agents (one per source) and merge their findings — see /agent-army.
Show full SKILL.md (249 more words)Show less
Step 2 — Extract signal from each source
For each reachable source, pull:
- Firmographics — industry/vertical, company size, geography, business model, tech stack.
- Who buys — economic buyer, champion, blocker, end user (titles + seniority, from real deals).
- Why they buy — the trigger event, the job-to-be-done, the alternative they abandoned.
- Why they don't — top closed-lost reasons, top objections, top churn reasons.
- Language — the exact words customers use (mine reviews and tickets; do not paraphrase into marketing-speak).
- Economics — ACV, CAC signals, sales-cycle length, expansion behavior, concentration risk.
Record sample sizes and date ranges for everything. Flag anything based on fewer than ~5 data points as "thin signal."
Step 3 — Synthesize the ICP
Write icp-profile.md:
# Ideal Customer Profile — {COMPANY}
Generated: {timestamp} · Sources scanned: {list} · Confidence: {High/Med/Low}
## The ICP in one sentence
{Vertical} companies of {size} who {trigger}, evaluated against {alternative}, where the champion is a {title} and the economic buyer is a {title}.
## Firmographic fit (with evidence)
- Industry: ... (evidence: N of M closed-won)
- Size: ...
- Geography / model / stack: ...
## Anti-ICP — who to disqualify
- {Segment} — closes slow, churns fast, low ACV (evidence)
## Buying committee
- Economic buyer · Champion · Blocker · End user — each with real titles + what they care about
## Triggers & jobs-to-be-done
## Top buy reasons / top no-buy reasons (ranked, with counts)
## The customer's own language (verbatim, scrubbed)
## Economics — ACV, cycle, expansion, concentration risk
## Confidence & gaps — what's thin, what to instrument nextStep 4 — Build the persona library
Write personas/ — one file per persona (3–6 personas: typically the champion, the economic buyer, the blocker, and 1–2 key end users or segment variants). Each persona file is structured so the panel skills can load it directly:
---
persona_id: ops-leader-champion
role: Champion
archetype: "VP of Operations at a 50–200 person services firm"
based_on: "12 closed-won champions, CRM trailing 12 mo"
---
# {Archetype name}
- Goals / success metrics:
- Pains (verbatim language):
- What earns trust / what triggers skepticism:
- Buying authority & budget reality:
- Objections they raise (real, from lost deals):
- How they talk (tone, vocabulary, 2–3 scrubbed quotes):
- What would make them a hard NO:Also write personas/index.md listing every persona, its role in the committee, and its evidence base.
Step 5 — Handoff
End with:
- A 5-line ICP summary the user can paste anywhere.
- "Sources I could not reach" and what auth/access would unlock them.
- "Confidence ledger" — which conclusions are strong vs. thin.
- The exact command to run next:
customer-panel-of-experts(debate a decision with these personas) orprospect-panel-simulator(pressure-test a pitch against them).
Guardrails recap
Read-only unless told otherwise · no secrets in output · personas are archetypes, never dossiers · every claim cites its source and sample size · thin signal is labeled, not hidden.
© OneWave-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in icp-deep-scanner of OneWave-AI/claude-skills.
Open the folder on GitHubat commit fc5b785
Compare with similar skills
Icp Deep Scanner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Icp Deep Scanner this skillOneWave-AI/claude-skills | 336 | — | ~1.8k | Automated safety check: Pass | MIT | |
| CRM Icp Analysiscognyai/claude-code-marketing-skills | 104 | — | ~2.2k | Automated safety check: Notes | None | |
| Sales And Revenue Operationsmanojbajaj95/claude-gtm-plugin | 105 | — | ~2.2k | Automated safety check: Pass | MIT | |
| GEO Prospect Trackerzubair-trabzada/geo-seo-claude | 11k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib | 154 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Sf DatacloudJaganpro/sf-skills | 424 | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Sales And Revenue Operations
manojbajaj95/claude-gtm-plugin
Comprehensive sales and revenue operations skill. An agent skill from manojbajaj95/claude-gtm-plugin.
GEO Prospect Tracker
zubair-trabzada/geo-seo-claude
Tracks GEO agency leads and clients through a sales pipeline in a local JSON file, with notes, audit scores, deal values and a pipeline summary.
Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
B2b Sdr Agent
iPythoning/b2b-sdr-agent-template
Open-source B2B AI SDR template. An agent skill from iPythoning/b2b-sdr-agent-template.
More from OneWave-AI/claude-skills
All 69 skills in this repoCRM Data Cleanup
OneWave-AI/claude-skills
Finds duplicate and junk records in a CRM CSV export with fuzzy matching, normalizes fields and writes a reviewable merge plan plus import-ready files without touching the live CRM.
Design Export Repair
OneWave-AI/claude-skills
Repairs broken decks and PDFs exported from Claude Design or similar AI deck generators: clipped text, wrong fonts and corrupted .pptx package structure.
Bi Measure Builder
OneWave-AI/claude-skills
Writes, explains, debugs, and optimizes BI calculations - Power BI / Fabric DAX measures and calculated columns, Tableau calculated fields (FIXED/INCLUDE/EXCLUDE LOD expressions, table…
Bookkeeping Close
OneWave-AI/claude-skills
Categorizes transactions, reconciles bank and card statements to the ledger, works a month-end checklist and prepares a close package, without ever forcing a balance.
CSV and Excel Merger
OneWave-AI/claude-skills
Combines CSV, TSV and Excel files into one verified table with pandas, by stacking or joining, mapping columns, normalizing keys and removing duplicates.
Sec Filing Puller
OneWave-AI/claude-skills
Pulls financial statement numbers for US public companies straight from SEC EDGAR's free official XBRL APIs (companyfacts, companyconcept, frames, submissions) into a cited table.
Related
Categories
Questions about Icp Deep Scanner
What does Icp Deep Scanner do?
Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library. Icp Deep Scanner is an agent skill from OneWave-AI/claude-skills. Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library.
When should I use Icp Deep Scanner?
Icp Deep Scanner fits situations like: you need to define; refresh your ICP; build buyer personas from real data instead of guesses; generate the persona inputs that the customer-panel-of-experts and prospect-panel-simulator skills consume.
How do I install Icp Deep Scanner in Claude Code?
Run `npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a claude-code`. Or copy the skill folder (icp-deep-scanner in OneWave-AI/claude-skills) into .claude/skills/icp-deep-scanner in your project. Claude Code loads it when a task matches its description.
How do I install Icp Deep Scanner in Codex?
Run `npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a codex`. Or copy the skill folder (icp-deep-scanner in OneWave-AI/claude-skills) into .agents/skills/icp-deep-scanner in your project. Codex loads it when a task matches its description.
Can I use Icp Deep Scanner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/icp-deep-scanner, .gemini/skills/icp-deep-scanner, .github/skills/icp-deep-scanner and .opencode/skills/icp-deep-scanner in your project.
What does Icp Deep Scanner need to run?
Going by SKILL.md and its folder, Icp Deep Scanner needs credentials named SUPABASE_TOKEN and OPENAI_API_KEY. Our summary lists: A credential in SUPABASE_TOKEN; A credential in OPENAI_API_KEY.
Does Icp Deep Scanner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Icp Deep Scanner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Icp Deep Scanner use?
Icp Deep Scanner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Icp Deep Scanner use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icp Deep Scanner?
Skills that share tags, products or a category with Icp Deep Scanner: CRM Icp Analysis (cognyai/claude-code-marketing-skills, 104 stars), Sales And Revenue Operations (manojbajaj95/claude-gtm-plugin, 105 stars), GEO Prospect Tracker (zubair-trabzada/geo-seo-claude, 11k stars) and Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icp Deep Scanner?
OneWave-AI (a GitHub organization) maintains it in OneWave-AI/claude-skills, which has 336 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on October 2, 2026.
Source: OneWave-AI/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.