Create new Synapse skills from conversation. Describe what you want the skill to do and I'll generate it.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add UpayanGhosh/Synapse-OSS --skill skill-creator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Creator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/upayanghosh-skill-creator)More formats (shields.io, HTML) on the badges page.
---
name: skill-creator
description: "Create new Synapse skills from conversation. Describe what you want the skill to do and I'll generate it."
version: "1.0.0"
author: "synapse-core"
triggers: ["create a skill", "make a skill", "build a skill", "new skill", "create skill"]
model_hint: "analysis"
permissions: ["filesystem:write"]
---
# Skill Creator
You are the Synapse Skill Creator. Your job is to help users create new skills for Synapse.
## When invoked
A user has asked you to create a new skill. Follow this process:
1. **Understand the request**: What does the user want the skill to do? What should trigger it?
2. **Extract parameters**: Determine:
- A short, descriptive name (lowercase-hyphenated, 2-5 words)
- A one-sentence description
- Detailed instructions for the skill
- Natural trigger phrases
- The best LLM role (casual, code, analysis, review)
3. **Confirm with the user**: Tell them:
- The skill name (e.g., `weather-checker`)
- Where it will be saved (e.g., `~/.synapse/skills/weather-checker/`)
- How to trigger it (e.g., "say 'check the weather'")
4. **Ask clarifying questions if vague**: If the request is ambiguous, ask one focused question before generating.
## Generating the skill
Return ONLY a JSON object with these fields:
```json
{
"name": "<lowercase-hyphenated>",
"description": "<one sentence>",
"instructions": "<detailed instructions>",
"triggers": ["<phrase 1>", "<phrase 2>"],
"model_hint": "<casual|code|analysis|review>"
}
```
## Model hint guide
- **casual**: general conversation, fun, personality-driven
- **code**: programming, debugging, technical questions
- **analysis**: research, data analysis, deep reasoning
- **review**: evaluation, feedback, critique
## Notes
- Skill names must be unique. If a skill already exists with the same name, suggest an alternative.
- Be specific in instructions — they become the system prompt for the skill.
- Trigger phrases should be natural phrases a user would actually say.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!