Adds task-specific guidance to your AI agent for writing content, building web projects and researching decisions.
cc-skills is Samuel Berthe’s collection of reusable instructions for AI agents. It covers marketing content, developer writing, web development, research and workplace communication. The writing skills include guides for defining a brand’s voice and prose style, alongside skills for producing articles, newsletters and announcements.
After installation, the agent uses skill descriptions to select relevant instructions and loads supporting references as needed. You can also invoke individual skills manually in tools that support that feature. Some tasks need additional tools, such as a metrics CLI or a separate skill for Word export; those conditions appear beside the relevant components.
Bring a topic, audience and examples for a technical article. Define reusable voice and prose guides for repeat publishing, then use the dedicated hook and CTA skills to develop the article’s opening and ending.
Work through Manifest V3 permissions, messaging, storage and background behavior. For a Vite-based extension, the CRXJS skill adds guidance on hot reload, content script imports and typed manifests.
Check a site’s analytics, legal requirements, security headers, search visibility, social previews and accessibility before publishing. The checklist also covers monitoring after launch.
Use the metrics skill to discover relevant metrics and build instant or range queries. This needs promql-cli, jq and a reachable metrics host; configure the host and any credentials yourself before asking the agent to query it.
Set a research question, scope and intended audience, then use the research workflow to compare sources and assemble a cited Markdown report. The agent needs web search and fetching tools for the research.
Work through a salary discussion, sales objection or disagreement over scope. The negotiation skill guides preparation, live coaching and diplomatic replies around the people and constraints involved.
Supply session details, participant feedback and outcomes to develop a structured Markdown draft. Exporting the approved report to Word requires the separate docx skill.
Showing all 21
Design article-ending calls to action, including copy, layout and A/B test plans.
Develop English or French titles and opening hooks for long-form articles.
Create or adapt PROSE.md guides for vocabulary, sentence structure and rhythm.
Define brand voice and channel-specific tone rules in TONE.md.
Edit French text to remove formulaic AI phrasing and restore voice.
Turn founder stories and business results into B2B LinkedIn posts.
Draft press announcements using regional and media-specific conventions.
Rewrite English technical documentation using ASD-STE100 Simplified Technical English rules.
Develop newsletter issues and web essays with voice, formatting and growth guidance.
Structure developer tutorials, explainers, benchmarks and postmortems around a clear thesis.
Research a topic across multiple sources and assemble a cited Markdown report.
Prepare negotiations, coach difficult conversations and draft diplomatic replies.
Draft workshop reports; Word export requires the separate docx skill.
Build Manifest V3 extensions, including permissions, messaging, storage and publishing.
Configure Vite-based extensions with CRXJS, hot reload and typed manifests.
Define UI typography, colors, components and design tokens in DESIGN.md.
Review analytics, legal requirements, security, SEO and accessibility before website launch.
Apply Conventional Commits conventions to commits, branches and worktree names.
Query Prometheus metrics; requires promql-cli, jq and a configured metrics host.
Decide what stays in SKILL.md and what belongs in reference files.
Restructure skill files to address snyk-agent-scan alerts; scanning requires a SNYK_TOKEN.
No matching results.
Install the skills together: some reference guidance in other skills.
Add the full skill collection with the Skills CLI. This installs the skills without registering the plugin. The default scope is your current project.
From your project directory, run this command in a terminal.
npx skills add https://github.com/samber/cc-skills --allClaude Code discovers project skills in .claude/skills/. Changes inside an existing skills directory load automatically; if the directory was created during the session, use Claude Code’s skill-reload action. Check the available skills in Claude Code.
Install the complete cc-skills plugin in a local Claude Code session. Locally installed plugins are unavailable in Claude Code cloud sessions.
In Claude Code, add Samuel Berthe’s plugin marketplace.
/plugin marketplace add samber/ccOpen cc-skills for installation, choose its scope in the plugin panel and install it.
/plugin install cc-skills@samberRead the installation summary. If it says the plugin is active, continue. If it requests a reload, close the panel to let Claude Code apply it; if a prompt-cache warning leaves the plugin pending, follow the reload guidance in the panel.
To confirm availability, type / in Claude Code and look for skills under cc-skills. The plugin also appears in the plugin panel’s Installed tab.
Add the full skill collection with the Skills CLI. This installs the skills without registering the plugin. The default scope is your current project.
From your project directory, run this command in a terminal.
npx skills add https://github.com/samber/cc-skills --allAntigravity discovers workspace skills in .agents/skills/. In the CLI, start a new conversation to load newly added skills. In the IDE, inspect active skills through Customizations in the agent side panel.
Install cc-skills as a plugin in GitHub Copilot CLI.
Run this command inside an interactive Copilot CLI session.
/plugin install https://github.com/samber/cc-skillsConfirm that cc-skills appears among the installed plugins and that its skills appear in Copilot CLI’s available-skills list.
Copy the skill collection into your personal Copilot skills directory for use across projects. This adds the skills without registering the plugin.
Run this command in a terminal.
git clone https://github.com/samber/cc-skills.git ~/.copilot/skills/cc-skillsStart a Copilot CLI session, or reload skills in your current session.
Check Copilot CLI’s available-skills list for the cc-skills entries.
Copy the skill collection into your personal Cursor skills directory. This adds the skills without registering the plugin.
Run this command in a terminal.
git clone https://github.com/samber/cc-skills.git ~/.cursor/skills/cc-skillsStart Cursor so it discovers the installed skills.
In Agent chat, type / and search for a skill from the collection.
Install cc-skills through Codex CLI. Plugins are available in Codex CLI and the ChatGPT desktop app; the IDE extension supports standalone skills but does not support plugins.
Run the plugin installation command in a terminal.
codex plugin add github:samber/cc-skillsStart a new Codex session before using the bundled skills.
Check that cc-skills appears in Codex’s plugin browser and that its skills appear in the available-skills list.
Use the manual fallback to add the collection to your personal skills directory. Standalone skills work in Codex CLI, the ChatGPT desktop app and the IDE extension; this method does not register the plugin.
Run this command in a terminal.
git clone https://github.com/samber/cc-skills.git ~/.agents/skills/cc-skillsCodex detects skill changes automatically. Check the available-skills list in the CLI or IDE extension, or Skills in the desktop app’s sidebar. If the new skills do not appear, restart Codex.
Add the full skill collection with the Skills CLI. This installs the skills without registering the plugin. The default scope is your current project.
From your project directory, run this command in a terminal.
npx skills add https://github.com/samber/cc-skills --allCodex discovers project skills in .agents/skills/ and detects changes automatically. Check the available-skills list in the CLI or IDE extension, or Skills in the desktop app’s sidebar. If the new skills do not appear, restart Codex.
Add the skill collection to your personal .agents/skills/ directory, which OpenCode supports for skill discovery. This installs skills without registering an OpenCode package plugin.
Run this command in a terminal.
git clone https://github.com/samber/cc-skills.git ~/.agents/skills/cc-skillsOpenCode lists permitted skills for the agent to load through its skill tool. Its documentation does not provide a user-facing skills-list command for checking this installation.
Install cc-skills as a Gemini CLI extension.
Run this command in a terminal, outside Gemini CLI’s interactive session.
gemini extensions install https://github.com/samber/cc-skillsRestart the Gemini CLI session to load the extension.
Check that cc-skills appears in the installed-extensions list and that its skills appear in the session’s available-skills list.
The cc-skills maintainer provides two ways to copy the full skill collection into OpenClaw’s skill directories. Both add the skills without registering the plugin.
Where should the skills be available?
Run this command in a terminal to copy the collection into ~/.openclaw/skills/. Skills there are shared across local agents unless agent allowlists restrict them.
git clone https://github.com/samber/cc-skills.git ~/.openclaw/skills/cc-skillsUse this option when your active OpenClaw workspace is ~/.openclaw/workspace. Run the command in a terminal to copy the collection into that workspace’s skills directory.
git clone https://github.com/samber/cc-skills.git ~/.openclaw/workspace/skills/cc-skillsStart a new OpenClaw session to load eligible skills from the selected directory.
Check OpenClaw’s skills list for the collection’s skills. Use its skill check or skill information view to inspect any missing requirements; the OpenClaw skills CLI reference describes these checks.