skill generator

Documentation Community

Skill notes

Trigger Words

"create a skill" "make a skill" "generate a skill" "build a skill" "new skill"

Phase 1: Requirements Gathering

Ask the user for skill specifications: Skill name: What should the skill be called? Description: What does the skill do? Trigger words: What words/phrases activate this skill? Functionality: What are the main features?

Phase 2: Skill Creation

Create a directory structure: /tmp/skill-{skillname}/ Generate the following files: SKILL.md: Main skill documentation with: Trigger words section Description

Phase 3: File Verification (Pre-Download)

List all created files in /tmp/skill-{skillname}/ Display file count and names to user Ask user to confirm files look correct before download

Phase 4: Download to User Machine

Copy all files from /tmp/skill-{skillname}/ to $OUTPUT_DIR/skill-{skillname}/ Maintain directory structure during copy Display success message with file list

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
85 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@lofcz · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.; The upstream repository has not been updated for 224 days and may not match current agent behavior.

Output preview skill-generator-lofcz.preview
# Usage Examples

**Example 1:** User: "{example user message}" Assistant: {what the assistant should do}

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.