Reusable SKILL.md instructions for Claude and OpenCode. Each skill lives in
its own directory and can be invoked by name, for example /fact-checker.
Visit the project website at kshyam.github.io/opencode-and-claude-skills. Download all skills as a ZIP from GitHub.
The website provides the simplest installation path:
/grill-me.Claude Code discovers project skills under .claude/skills/. From the root of
this repository, copy the skills into a project-local Claude directory:
mkdir -p .claude/skills
for skill in */; do
if [ -f "$skill/SKILL.md" ]; then
cp -R "$skill" .claude/skills/
fi
done
For skills available across all Claude Code projects, use
~/.claude/skills/ instead of .claude/skills/. Restart Claude Code if the
skills do not appear, then invoke one directly with /skill-name.
OpenCode loads one skill per directory when that directory contains a
SKILL.md. It supports project-local and global installation.
Run this from the root of this repository, or replace the destination with the project where you want the skills available:
mkdir -p .opencode/skills
for skill in */; do
if [ -f "$skill/SKILL.md" ]; then
cp -R "$skill" .opencode/skills/
fi
done
OpenCode will discover the skills when started from that project. You can
also use .claude/skills/ or .agents/skills/ for compatible project skill
locations.
To make the skills available in every OpenCode project:
mkdir -p ~/.config/opencode/skills
for skill in */; do
if [ -f "$skill/SKILL.md" ]; then
cp -R "$skill" ~/.config/opencode/skills/
fi
done
In OpenCode, ask for the task normally and let it choose a matching skill. To request one explicitly, mention its name in your prompt. For example:
Use the fact-checker skill to review the claims in this draft before I publish it.
If a skill does not appear, check that:
SKILL.md.name are the same.name and description.permission.skill rule.See the OpenCode skills documentation for discovery and permission details.
In Claude, invoke a skill with the command shown below. In OpenCode, use the matching skill name in a normal request or let OpenCode select it automatically.
| Command | Purpose |
|---|---|
/5 |
Turn a rough request into a ready-to-send Opus 4.8 chat prompt |
/48 |
Turn a rough request into a ready-to-send Opus 4.8 chat prompt |
/client-brief |
Prepare a prospect brief before a client call |
/deck-builder |
Outline and build a presentation deck |
/deep-research-synthesizer |
Synthesize large source sets into grounded findings |
/delete-ai-words |
Remove common AI-sounding wording |
/excel-style |
Apply a personal style to spreadsheet work |
/fact-checker |
Verify factual claims against primary sources |
/fable-prompter |
Turn a rough request into a Fable 5 chat prompt |
/grill-me |
Interview before starting a substantial build |
/handoff |
Create a structured handoff for continuing later |
/hormozi-viral-1 |
Write a contrarian, list-based LinkedIn post |
/how-to |
Coach a beginner through an AI workflow step by step |
/humanizer |
Make writing sound more natural and less robotic |
/i-have-adhd |
Format responses for an ADHD reader |
/infographic-builder |
Turn content into a shareable infographic |
/linkedin-hook |
Generate LinkedIn post hooks |
/linkedin-post-report |
Analyze an Apify LinkedIn post export |
/meeting-notes |
Turn a meeting transcript into notes and actions |
/my-viral-post |
Draft a LinkedIn post from a personal content report |
/negotiation |
Build a negotiation strategy playbook |
/personal-voice |
Calibrate and apply the user’s writing voice |
/prompt-master |
Restructure a messy request into a task specification |
/reddit-researcher |
Research recent signals across social and web sources |
/red-pen |
Critique and rewrite important writing before delivery |
/tc-social-carousel |
Build a TC Social Instagram carousel |
/viral-recipe |
Capture and reproduce a viral post’s structure |
/write-a-skill |
Create a new SKILL.md skill |
/xlsx |
Create, clean, analyze, or format spreadsheets |
excel-style/SKILL.md contains template placeholders such as [ YOUR NAME ]; customize those before using it.SKILL.md before relying on a workflow in a new environment.