Software development
Skill toolbox-playground/super-claudio/skills/software-development
Software development skill. Use when the user wants to build, code, automate, or deploy anything technical. Covers backend APIs, databases, workflow automation, scripts, free public APIs, and hosting/deployment. Trigger on backend: "build an API", "REST API", "database schema", "Supabase", "Firebase", "PostgreSQL", "MongoDB", "FastAPI", "Express", "Fastify", "GraphQL", "Node.js server", "Python API", "Prisma", "ORM", "authentication backend", "serverless functions". Trigger on automation: "automate this", "connect these apps", "n8n", "Make.com", "Zapier", "when X happens do Y", "no-code automation", "schedule a script", "webhook", "automate posting", "IFTTT", "auto-post to Instagram", "batch processing", "automate email". Trigger on free APIs: "free API for X", "public API", "build a weather app", "NASA API", "real-time data", "open data", "free data source", "API without credit card", "government API". Trigger on deployment: "deploy my app", "Docker", "Railway", "GitHub Actions", "CI/CD", "hosting", "go live", "containerize", "VPS setup". Trigger on git/GitHub: "create a PR", "open a pull request", "GitHub CLI", "gh pr", "gh issue", "connect Claude to GitHub", "GitHub MCP", "commit message", "git workflow", "manage issues", "review a PR", "GitHub Actions workflow", "release on GitHub". Do NOT trigger for: frontend/UI design (use design skill), media generation (use media-content-creation).From its SKILL.md
npx -y skills add toolbox-playground/super-claudio --skill software-developmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.8 KB, 541 tokens by cl100k_base, as published. Nobody here has run it
Software Development
You are an expert developer. Route based on what the user needs to build or automate:
Routing
Backend Development
| Intent | Reference file |
|---|---|
| Database setup, schema design, ORM, queries | references/databases.md |
| API design, REST/GraphQL, framework selection, endpoints | references/apis.md |
| Deployment, hosting, Docker, CI/CD, going live | references/deployment.md |
For full-stack features: start with databases.md (schema), then apis.md (endpoints), then deployment.md (go live).
Workflow Automation
| Intent | Reference file |
|---|---|
| Visual workflow builder, n8n self-hosted, app integrations | references/automation-n8n.md |
| Cloud-based no-code automation (Make.com, Zapier) | references/automation-cloud.md |
| Python/Bash scripting, file processing, cron jobs | references/automation-scripting.md |
Quick decision:
- Free + self-hosted + powerful → n8n
- Fast setup + no server → Make.com or Zapier
- Technical user + full control → Python scripting
Free Public APIs
| Domain | Reference file |
|---|---|
| Geography, weather, climate, natural events | references/free-apis-geo.md |
| Finance, space, sports, news, and all other domains | references/free-apis-catalog.md |
Git & GitHub
| Intent | Reference file |
|---|---|
| Git workflow, branches, commits, undoing changes | references/git-and-github.md |
GitHub CLI (gh pr, gh issue, gh release) | references/git-and-github.md |
| GitHub MCP server (Claude reads/writes GitHub directly) | references/git-and-github.md |
| GitHub Actions, CI/CD workflows | references/git-and-github.md |
Testing & Security
| Intent | Reference file |
|---|---|
| Unit/integration/E2E tests (pytest, Jest, Playwright) | references/testing-and-security.md |
| Security checklist, OWASP, secrets detection, dependency scanning | references/testing-and-security.md |
Installed Plugins Reference
For Claude Code plugins already installed that extend development capabilities:
→ references/plugins.md
When to check for more tools
If none of these fit, invoke super-claudio:discover to search community marketplaces for
newer or more specialized development tools.
What ships with it: 11 files
39.3 KB alongside SKILL.md
references/
- apis.md2.9 KB
- automation-cloud.md2.2 KB
- automation-n8n.md2.1 KB
- automation-scripting.md3.1 KB
- databases.md2.7 KB
- deployment.md2.5 KB
- free-apis-catalog.md9.1 KB
- free-apis-geo.md3.0 KB
- git-and-github.md5.2 KB
- plugins.md1.9 KB
- testing-and-security.md4.8 KB
Gives 0 of the 12 instructions most pr commit review skills give in 541 tokens
Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06
- Use conventional commit message formatin 150 of 1055, across 145 files
- Announce skill usage at startin 78 of 1055
- Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
- Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
- Use imperative mood for commit subjectin 52 of 1055
- Run tests to verify clean baselinein 42 of 1055, across 32 files
- Push branch to originin 40 of 1055, across 38 files
- Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
- Delete branches after mergingin 38 of 1055, across 30 files
- Create worktree with new branchin 37 of 1055, across 32 files
- Wrap body text at 72 charactersin 36 of 1055, across 34 files
- Auto-detect and run project setupin 35 of 1055, across 27 files
Said here and by no other author read
- route requests based on build or automation needs
- design database schema before building API endpoints
- build API endpoints before deployment
- use n8n for self-hosted automation
- use Make or Zapier for cloud-based automation
- use Python or Bash for scripting tasks
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.