SkillsAdd

smithery/kevinswiber

gumbo-init

Initialize a gumbo directory for the current project, creating a template in ~/.gumbo and a symlink in the project repo

Installation

$ npx skills add smithery/kevinswiber --skill gumboinit
View on skills.sh ↗ Website ↗

Also in this package

Other skills from smithery/kevinswiber.

npx skills add smithery/kevinswiber
research-archive 0

Browse all from smithery/kevinswiber

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(*/gumbo-init/scripts/init.sh:*), Read, Write, Edit
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,086 B
  • docs SUMMARY.md 136 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Your task

  1. Check if the user provided a project name (e.g. /gumbo-init myapp). If they did, pass it as the third argument to the init script. If not, omit the third argument and the script will default to the directory name.
  1. Run the gumbo init script:
# With project name:
./scripts/init.sh ~/.gumbo "$PWD" <project-name>

# Without project name (defaults to directory name):
./scripts/init.sh ~/.gumbo "$PWD"
  1. After successful initialization, remind the user to add the gumbo data directory to their Claude Code context so it's available across sessions. Tell them to run:
/add-dir ~/.gumbo

They can add it to either the current project or to their user-scoped settings (~/.claude/settings.json) if they want it available in all projects.

Report the output to the user. Do not use any other tools or do anything else.