Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
How humans and AI compose in content workflows. An agent skill from rampstackco/claude-skills.
$ npx skills add rampstackco/claude-skills --skill ai-content-collaboration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills ai-content-collaboration --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/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ai-content-collaboration .claude/skills/ai-content-collaboration && 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 "ai-content-collaboration" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/ai-content-collaboration into .claude/skills/ai-content-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-content-collaboration", 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/rampstackco/claude-skills/tree/main/skills/ai-content-collaborationType 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 rampstackco/claude-skills --skill ai-content-collaboration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills ai-content-collaboration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ai-content-collaboration .agents/skills/ai-content-collaboration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ai-content-collaboration" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/ai-content-collaboration into .agents/skills/ai-content-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-content-collaboration", 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 rampstackco/claude-skills --skill ai-content-collaboration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills ai-content-collaboration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ai-content-collaboration .cursor/skills/ai-content-collaboration && 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 "ai-content-collaboration" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/ai-content-collaboration into .cursor/skills/ai-content-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-content-collaboration", 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/rampstackco/claude-skills.git --path skills/ai-content-collaboration--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 rampstackco/claude-skills --skill ai-content-collaboration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills ai-content-collaboration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ai-content-collaboration .gemini/skills/ai-content-collaboration && 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 "ai-content-collaboration" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/ai-content-collaboration into .gemini/skills/ai-content-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-content-collaboration", 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 rampstackco/claude-skills ai-content-collaborationInstalls 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 rampstackco/claude-skills --skill ai-content-collaboration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ai-content-collaboration .github/skills/ai-content-collaboration && 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 "ai-content-collaboration" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/ai-content-collaboration into .github/skills/ai-content-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-content-collaboration", 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 rampstackco/claude-skills --skill ai-content-collaboration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rampstackco/claude-skills ai-content-collaboration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ai-content-collaboration .opencode/skills/ai-content-collaboration && 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 "ai-content-collaboration" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/ai-content-collaboration into .opencode/skills/ai-content-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-content-collaboration", 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.
ai-content-collaborationHow humans and AI compose in content workflows. An agent skill from rampstackco/claude-skills.
AI Content Collaboration is an agent skill from rampstackco/claude-skills. How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also…
Its SKILL.md is about 5.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `references/ai-participation-boundaries.md` and `references/ai-slop-detection-and-avoidance.md`).
It sits in Business, Finance & HR, covering Performance reviews. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
AI Content Collaboration loads about 5.6k tokens when it runs, and up to ~26k if it reads all its reference files. Until then it costs about 181 tokens; SKILL.md has 2,851 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.
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.
The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 2,851 words, ~5,647 tokens.
.claude/skills/ai-content-collaboration/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.A senior editorial leader's playbook for how humans and AI compose in content workflows. Pragmatic, tool-agnostic, honest about both what AI in the loop enables and what it threatens.
Most content programs in 2026 use AI somewhere in the workflow. Pretending otherwise is dishonest; treating AI as a magic content factory is the failure mode this skill exists to prevent. The discipline is in between: knowing where AI legitimately accelerates, where humans must own, what hybrid patterns produce work that earns reader trust, and what crosses the line into AI slop or intellectual dishonesty.
This skill is the WORKFLOW layer that composes with every other content skill. Briefs can be AI-assisted; hub architectures can be AI-assisted; programmatic SEO is almost always AI-involved; editorial QA now includes AI-content audit by necessity. The collaboration discipline applies to all production stages, not to a single artifact type.
The voice is pragmatic and tool-agnostic deliberately. The methodology applies whether the AI in your loop is one of the major commercial models, an open-source model, or whatever ships next quarter. What stays constant is the workflow shape, the participation boundaries, the voice ownership question, and the ethical frame. What changes is which specific tool you reach for, which is implementation work that varies by team and budget.
When to use this skill: building or refining an AI-content workflow, calibrating a team on consistent AI usage, addressing the "we use AI but our work feels generic" problem, designing disclosure policies, or working through the ethics of AI-assisted content production for a regulated or trust-sensitive context.
This skill spans the workflow layer of AI-assisted content production. It composes with all six other content-suite skills as the cross-cutting discipline.
content-strategy is program scope: what to produce. Strategy decisions can be AI-assisted; the program-level judgment stays human.pillar-content-architecture is hub scope: how the topical hub fits together. Hub architecture can be AI-suggested; the architectural commitment stays human.content-brief-authoring is per-piece scope: briefs each piece. Briefs can be AI-drafted from research; the contract decisions stay human.content-and-copy is execution scope: writes each piece. Drafts can be AI-produced; voice and editorial judgment stay human.programmatic-seo is scaled scope: generates pages from data. AI generation is the dominant production model; sampling QA is the human gate.editorial-qa is gate scope: verifies before publish. AI-content audit is now a load-bearing gate; the audit's judgment stays human.The audience: editorial leaders, content directors, content ops managers, agencies running AI-assisted production, in-house teams calibrating AI usage across writers. The voice is senior editorial leader to junior editor or content marketer. Pragmatic, honest, tool-agnostic.
What is not in scope: specific prompts (those are implementation; teams develop their own), specific tool endorsements (the methodology applies regardless of which tool is in the loop), specific integration code (varies by stack and team). Tool categories appear when they earn methodology relevance; specific tools appear only as illustrations of categories, never as recommendations.
The keystone framing.
The pathology to avoid is treating AI as either a magic content factory (cheap, fast, scaled, output quality optional) OR as a forbidden intruder (purity gospel that does not survive contact with deadlines). Both readings produce bad work.
The discipline that produces durable work: humans own the content; AI accelerates the work. Specifically:
Humans own. Editorial judgment, voice, distinctive POV, fact accuracy, ethical decisions, what to publish versus what to kill, brand voice, narrative arc, tone calibration, reader empathy, claim verification.
AI accelerates. Research synthesis, draft generation against a brief, copy edit suggestions, alternative phrasings, summary, transcription, quality-control automation at scale.
The line. AI does work that the human directs and verifies. AI does NOT make decisions about what publishes, who is quoted, what is true, or what voice the brand uses.
The litmus test. If your AI-assisted piece publishes without a human being able to defend every claim, every position, and every word, you have crossed the line. The piece is AI's work, dressed in your byline. Readers eventually notice.
A non-exhaustive list of stages where AI in the loop is fine and often improves the work.
In each case, AI accelerates work the human still owns. The acceleration is real; the ownership stays unchanged.
Detail in references/ai-participation-boundaries.md.
The boundary list.
The "human in the loop" framing is necessary but insufficient. A human briefly reviewing AI-generated content before publish is not ownership; it is rubber-stamping. Ownership requires the human to have made the actual decisions the piece embodies.
Five patterns that work, with tradeoffs.
1. AI-first draft, human-edit-heavy. AI produces a 90% draft; the human spends 60% of the time editing. Output: efficient for high-volume editorial; risks generic voice if editing is light.
2. Human-first outline + research, AI-draft, human-rewrite. Human builds the outline and gathers research; AI drafts within that scaffold; human rewrites in voice. Output: preserves voice better; slower than AI-first.
3. AI-as-research-assistant, human-writes. AI condenses sources into a brief; human writes the entire piece from the brief. Output: highest voice fidelity; slowest.
4. Human-writes, AI-as-editor. Human drafts; AI suggests edits, alternative phrasings, copy edits; human accepts or rejects. Output: writer voice preserved; AI catches details.
5. AI-generates-at-scale, human-samples. For programmatic SEO. AI generates thousands of pages; human samples 50 to 200 with editorial-qa discipline. Output: scaled production; depends entirely on template quality and sampling discipline.
The pattern that fits depends on volume, voice sensitivity, team skill, and time budget. No pattern is "the right one"; pattern selection is a real decision that should match the production context.
Detail in references/hybrid-workflow-patterns.md.
Voice is the dominant casualty of careless AI workflows. The patterns that preserve voice.
The honest framing. Voice is the hardest thing to preserve in AI-assisted work and the easiest thing to lose. Programs that do not actively preserve voice end up with content that is technically correct, semantically generic, and indistinguishable from competitors using the same tools.
Detail in references/voice-ownership-preservation.md.
AI slop is the term of art for AI-generated content that is technically functional but reads as generic, derivative, and signal-less. Cross-reference editorial-qa's ai-content-audit-patterns reference for the detection patterns; this section addresses prevention.
Patterns that produce slop.
Patterns that prevent slop.
content-brief-authoring)The reader-detection problem. Readers can often sense AI-flavored content even when they cannot articulate why. Generic openings, predictable structures, "perfect" grammar that is emotionally flat. Slop loses reader trust over time even when individual pieces are not penalized.
Detail in references/ai-slop-detection-and-avoidance.md and cross-reference editorial-qa's audit patterns.
When should AI usage be disclosed to readers?
The tiered framework.
The principle. Disclose when the reader's understanding of the content's origin would change their trust in it. A bylined opinion piece purportedly by a named expert that is substantially AI-drafted is a trust violation; a product description on an ecommerce site that was AI-drafted is not.
Disclosure language patterns (when used).
Industry-specific norms vary. Major journalism organizations have published explicit AI usage standards. Content marketing has weaker norms but is moving toward disclosure for high-trust pieces.
Detail in references/disclosure-and-transparency-patterns.md.
Inconsistent AI usage across a team produces inconsistent output. The discipline.
The pathology. AI usage emerges informally, every writer develops their own patterns, output drifts, editors cannot pinpoint why pieces feel off. The discipline is making AI usage explicit, calibrated, and documented.
Detail in references/team-training-and-calibration.md.
AI tools were trained on copyrighted material. That is the simple ethical reality of every major LLM in 2026. The catalog's position on this question is not "AI use is unethical" (that would render the catalog itself hypocritical) but "intellectual honesty about AI involvement is non-negotiable."
The principles.
The intellectual-honesty frame supersedes any specific policy debate. Teams that treat AI usage with intellectual honesty produce content readers can trust over time. Teams that hide, deny, or rationalize lose trust eventually.
Detail in references/ethics-and-intellectual-honesty.md.
Rapid-fire. Diagnoses in references/common-collaboration-failures.md.
When designing or auditing an AI-assisted content workflow, walk these 12 considerations.
The output of the framework is a workflow document the team can reference: AI participation rules named, hybrid pattern selected, voice preservation patterns specified, disclosure tier set, calibration cadence committed, ethical floor articulated, accountable signer named for each piece.
references/ai-participation-boundaries.md - Where AI legitimately helps, where humans must own. The boundary list and the "human-in-the-loop is not ownership" distinction.references/hybrid-workflow-patterns.md - Five workflow patterns with tradeoffs and selection criteria. When each pattern fits production context.references/voice-ownership-preservation.md - Voice guidelines as prompt input, sample text as voice anchor, mid-draft voice check, final pass in human voice, reject-the-bland discipline.references/ai-slop-detection-and-avoidance.md - What produces slop, what prevents it. Cross-references editorial-qa's audit patterns.references/disclosure-and-transparency-patterns.md - Tiered disclosure framework, language patterns, industry norms.references/team-training-and-calibration.md - Documented policy, calibration sessions, voice library, quality benchmarks, onboarding.references/quality-calibration-with-ai-in-loop.md - How editorial standards shift when AI is in the workflow. Same standards, different failure modes.references/ethics-and-intellectual-honesty.md - Training data, attribution, fabrication boundaries, intellectual honesty as the supervening frame.references/common-collaboration-failures.md - 11+ failure patterns with diagnoses and fixes.AI in content workflows is neither magic nor menace. It is a category of tooling that, like every tooling category before it, rewards disciplined use and punishes careless use. The teams producing memorable AI-assisted content are the ones holding the line on human ownership, voice, fact accuracy, and intellectual honesty. The teams producing AI slop are the ones treating AI as a content factory.
The discipline is not anti-AI; it is pro-craft. Craft was always what made content worth reading; AI does not change that, it just raises the cost of skipping it.
When in doubt about whether an AI-assisted workflow is ready, ask: is human ownership specified, are participation boundaries documented, is voice preservation built into the prompt and review patterns, is fact verification a halt-condition, is disclosure tiered to audience trust, is the team calibrated, and is the ethical floor explicit? If yes to all of those, the workflow is ready. If no to any, the gap is where the program will produce slop and lose reader trust.
© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 10 other files (references) in skills/ai-content-collaboration of rampstackco/claude-skills.
Open the folder on GitHubat commit 482c9bf
AI Content Collaboration 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 |
|---|---|---|---|---|---|---|
| AI Content Collaboration this skillrampstackco/claude-skills | 935 | — | ~5.6k | Automated safety check: Pass | MIT | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 234 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Align Humanagentscope-ai/OpenJudge | 867 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Performance ReportAffitor/affiliate-skills | 698 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Run Mv Hoi Reconstructionnvidia-isaac/video_to_data | 847 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Company Analysiszhu1090093659/dsh-trading | 230 | — | ~4.2k | Automated safety check: Pass | Custom licence |
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
agentscope-ai/OpenJudge
A skill your agent uses when the user has a judge/grader and human-labeled data, and wants to measure how well the judge agrees with humans, detect systematic biases, determine whether automatic…
Affitor/affiliate-skills
Generate affiliate performance reports with KPIs and recommendations.
nvidia-isaac/video_to_data
Run and validate the repository-local multi-view camera calibration and human-object reconstruction pipelines.
zhu1090093659/dsh-trading
A skill your agent uses when the user wants to analyze a listed company, stock, business, or investment target; challenge or revise an existing company report; compare A/H or primary-listing/ADR…
CliMA/EnsembleKalmanProcesses.jl
Scaffold and maintain a SLURM/HPC job-dependency tree for an EnsembleKalmanProcesses.jl (EKP) calibration pipeline.
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
rampstackco/claude-skills
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
Categories
How humans and AI compose in content workflows. An agent skill from rampstackco/claude-skills. AI Content Collaboration is an agent skill from rampstackco/claude-skills. How humans and AI compose in content workflows.
AI Content Collaboration fits situations like: AI content workflow; AI-assisted writing; hybrid content production; AI in editorial.
Run `npx skills add rampstackco/claude-skills --skill ai-content-collaboration -a claude-code`. Or copy the skill folder (skills/ai-content-collaboration in rampstackco/claude-skills) into .claude/skills/ai-content-collaboration in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rampstackco/claude-skills --skill ai-content-collaboration -a codex`. Or copy the skill folder (skills/ai-content-collaboration in rampstackco/claude-skills) into .agents/skills/ai-content-collaboration in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill ai-content-collaboration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ai-content-collaboration, .gemini/skills/ai-content-collaboration, .github/skills/ai-content-collaboration and .opencode/skills/ai-content-collaboration in your project.
SKILL.md names no scripts, command-line tools or credentials: AI Content Collaboration is instructions for the agent only.
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.
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.
AI Content Collaboration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.6k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 20k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with AI Content Collaboration: Wp Performance Review (elvismdev/claude-wordpress-skills, 234 stars), Align Human (agentscope-ai/OpenJudge, 867 stars), Performance Report (Affitor/affiliate-skills, 698 stars) and Run Mv Hoi Reconstruction (nvidia-isaac/video_to_data, 847 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.
Source: rampstackco/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.