Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Create skills by learning from high-quality GitHub projects. An agent skill from GBSOSS/skill-from-masters.
Install Skill From GitHub
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-github -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-github --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/GBSOSS/skill-from-masters.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-from-github .claude/skills/skill-from-github && 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 "skill-from-github" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-github into .claude/skills/skill-from-github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-github", 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/GBSOSS/skill-from-masters/tree/main/skills/skill-from-githubType 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 GBSOSS/skill-from-masters --skill skill-from-github -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-github --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-from-github .agents/skills/skill-from-github && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-from-github" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-github into .agents/skills/skill-from-github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-github", 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 GBSOSS/skill-from-masters --skill skill-from-github -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-github --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-from-github .cursor/skills/skill-from-github && 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 "skill-from-github" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-github into .cursor/skills/skill-from-github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-github", 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/GBSOSS/skill-from-masters.git --path skills/skill-from-github--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 GBSOSS/skill-from-masters --skill skill-from-github -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-github --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-from-github .gemini/skills/skill-from-github && 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 "skill-from-github" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-github into .gemini/skills/skill-from-github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-github", 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 GBSOSS/skill-from-masters skill-from-githubInstalls 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 GBSOSS/skill-from-masters --skill skill-from-github -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-from-github .github/skills/skill-from-github && 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 "skill-from-github" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-github into .github/skills/skill-from-github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-github", 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 GBSOSS/skill-from-masters --skill skill-from-github -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-github --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-from-github .opencode/skills/skill-from-github && 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 "skill-from-github" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-github into .opencode/skills/skill-from-github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-github", 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
skill-from-github- GitHub stars
- 1.6k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 466 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create skills by learning from high-quality GitHub projects. An agent skill from GBSOSS/skill-from-masters.
- Works in 6 steps: Understand User Intent → Search GitHub → Present Options to User → …
- Agent Workflows work in your project
- SKILL.md covers When to Use, Workflow, Example and Important Notes, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill From GitHub is an agent skill from GBSOSS/skill-from-masters. Create skills by learning from high-quality GitHub projects
Its SKILL.md is about 1.2k 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 Agent Workflows. It works with GitHub. The repository describes itself as: Stand on the shoulders of giants — Create AI skills built on proven methodologies from domain experts. The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/skill-from-github”
Workflow steps
6 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 c4d27d2. 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill From GitHub loads about 1.2k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 466 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 GBSOSS/skill-from-masters at commit c4d27d2, republished under its MIT licence (© GBSOSS). 466 words, ~1,213 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-from-github/SKILL.md (or your agent's skills folder).- name
- skill-from-github
- description
- Create skills by learning from high-quality GitHub projects
- model
- sonnet
Skill from GitHub
When users want to accomplish something, search GitHub for quality projects that solve the problem, understand them deeply, then create a skill based on that knowledge.
When to Use
When users describe a task and you want to find existing tools/projects to learn from:
- "I want to be able to convert markdown to PDF"
- "Help me analyze sentiment in customer reviews"
- "I need to generate API documentation from code"
Workflow
Step 1: Understand User Intent
Clarify what the user wants to achieve:
- What is the input?
- What is the expected output?
- Any constraints (language, framework, etc.)?
Step 2: Search GitHub
Search for projects that solve this problem:
{task keywords} language:{preferred} stars:>100 sort:starsSearch tips:
- Start broad, then narrow down
- Try different keyword combinations
- Include "cli", "tool", "library" if relevant
Quality filters (must meet ALL):
- Stars > 100 (community validated)
- Updated within last 12 months (actively maintained)
- Has README with clear documentation
- Has actual code (not just awesome-list)
Step 3: Present Options to User
Show top 3-5 candidates:
## Found X projects that can help
### Option 1: [project-name](github-url)
- Stars: xxx | Last updated: xxx
- What it does: one-line description
- Why it's good: specific strength
### Option 2: ...
Which one should I dive into? Or should I search differently?Wait for user confirmation before proceeding.
Step 4: Deep Dive into Selected Project
Once user selects a project, thoroughly understand it:
- Read README - Understand purpose, features, usage
- Read core source files - Understand how it works
- Check examples - See real usage patterns
- Note dependencies - What it relies on
- Identify key concepts - The mental model behind it
Extract:
- Core algorithm/approach
- Input/output formats
- Error handling patterns
- Best practices encoded in the code
Step 5: Summarize Understanding
Present what you learned to user:
## Understanding [project-name]
### Core Approach
How it solves the problem...
### Key Techniques
1. ...
2. ...
### Limitations
- ...
### What I'll encode in the skill
- ...
Does this look right? Should I proceed to create the skill?Wait for user confirmation.
Show full SKILL.md (214 more words)Show less
Step 6: Create Skill via skill-creator
Hand off to skill-creator with:
- Clear purpose - What the skill does
- Methodology - The approach learned from the project
- Step-by-step process - Concrete instructions
- Quality criteria - What good output looks like
- Common pitfalls - What to avoid (learned from project issues/docs)
Important: The skill should encode the knowledge from the project, not just wrap the tool. The skill should work even without the original project installed.
Example
User: "I want to write better commit messages"
Step 2 - Search:
commit message convention stars:>100 sort:starsStep 3 - Present:
## Found 4 projects
### Option 1: conventional-commits/conventionalcommits.org (4.2k ⭐)
- Specification for human and machine readable commit messages
- Why: Industry standard, used by Angular, Vue, etc.
### Option 2: commitizen/cz-cli (15k ⭐)
- CLI tool for creating conventional commits
- Why: Battle-tested, lots of adapters
### Option 3: carloscuesta/gitmoji (14k ⭐)
- Emoji guide for commit messages
- Why: Visual, fun approach
Which one interests you?User: "Let's go with conventional commits"
Step 4 - Deep dive:
- Read the specification
- Understand types (feat, fix, docs, etc.)
- Learn about scopes, breaking changes
- Study real-world examples
Step 5 - Summarize:
## Understanding Conventional Commits
### Core Approach
Structured format: <type>(<scope>): <description>
### Key Types
- feat: new feature
- fix: bug fix
- docs: documentation
- ...
### Benefits Learned
- Automated changelog generation
- Semantic versioning
- Clear history
Ready to create a commit message skill based on this?Step 6 - Create skill with these principles encoded
Important Notes
- Always get user confirmation - At step 3 (project selection) and step 5 (before creating)
- Prefer learning over wrapping - Encode the knowledge, not just "run this tool"
- Check license - Mention if project has restrictive license
- Credit the source - Include attribution in generated skill
- Quality over speed - Take time to truly understand the project
What This Skill is NOT
- NOT a package installer
- NOT a tool wrapper
- It's about learning from the best projects and encoding that knowledge into a reusable skill
© GBSOSS, 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 skills/skill-from-github of GBSOSS/skill-from-masters.
Open the folder on GitHubat commit c4d27d2
Compare with similar skills
Skill From GitHub 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 |
|---|---|---|---|---|---|---|
| Skill From GitHub this skillGBSOSS/skill-from-masters | 1.6k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Diagnosing Superpowers Sessionsobra/superpowers | 297k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Auto Skill Buildertradecatlabs/vibe-coding-cn | 17k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Skill Seekers Builderyusufkaraaslan/Skill_Seekers | 15k | — | ~760 | Automated safety check: Pass | MIT | |
| Repomix Codebase Packeryamadashy/repomix | 29k | — | ~1.3k | Automated safety check: Notes | MIT |
Similar skills
Auto Skill Builder
tradecatlabs/vibe-coding-cn
Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire.
- Official
Agentic Workflow Designer
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
Skill Seekers Builder
yusufkaraaslan/Skill_Seekers
Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.
Repomix Codebase Packer
yamadashy/repomix
Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.
Context Mode Ops
mksglu/context-mode
Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.
More from GBSOSS/skill-from-masters
Skill From Masters
GBSOSS/skill-from-masters
通过真实案例创建高质量skill。先找黄金案例和失败案例，归纳什么有效什么无效，再用理论解释为什么。skill是干活的，要从实践中学习，不是从书本中学习。触发词："帮我创建一个skill"、"我想做一个skill来..."
Skill From Notebook
GBSOSS/skill-from-masters
Extract methodologies from documents or examples to create executable skills
Search Skill
GBSOSS/skill-from-masters
Search and recommend Claude Code skills from trusted marketplaces
Related
Works with
Categories
Questions about Skill From GitHub
What does Skill From GitHub do?
Create skills by learning from high-quality GitHub projects. An agent skill from GBSOSS/skill-from-masters. Skill From GitHub is an agent skill from GBSOSS/skill-from-masters.
When should I use Skill From GitHub?
Skill From GitHub fits situations like: agent Workflows work in your project.
How do I install Skill From GitHub in Claude Code?
Run `npx skills add GBSOSS/skill-from-masters --skill skill-from-github -a claude-code`. Or copy the skill folder (skills/skill-from-github in GBSOSS/skill-from-masters) into .claude/skills/skill-from-github in your project. Claude Code loads it when a task matches its description.
How do I install Skill From GitHub in Codex?
Run `npx skills add GBSOSS/skill-from-masters --skill skill-from-github -a codex`. Or copy the skill folder (skills/skill-from-github in GBSOSS/skill-from-masters) into .agents/skills/skill-from-github in your project. Codex loads it when a task matches its description.
Can I use Skill From GitHub 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 GBSOSS/skill-from-masters --skill skill-from-github -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-from-github, .gemini/skills/skill-from-github, .github/skills/skill-from-github and .opencode/skills/skill-from-github in your project.
What does Skill From GitHub need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill From GitHub is instructions for the agent only.
Does Skill From GitHub 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 Skill From GitHub 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 Skill From GitHub use?
Skill From GitHub 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 Skill From GitHub use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Skill From GitHub?
Skills that share tags, products or a category with Skill From GitHub: Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Auto Skill Builder (tradecatlabs/vibe-coding-cn, 17k stars), Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars) and Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill From GitHub?
GBSOSS (a GitHub organization) maintains it in GBSOSS/skill-from-masters, which has 1,588 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on February 16, 2026.
Source: GBSOSS/skill-from-masters on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.