Gemini Skill Creator

3. Writing Principles (The "Claude Way")

When writing the body of SKILL.md, adhere to these best practices:

• Conciseness: Assume the agent is smart. Do not explain what a PDF or a Git repo is. Focus only on the unique logic of the skill.
• Progressive Disclosure: Keep SKILL.md under 500 lines. If more detail is needed, link to secondary files (e.g., [See ADVANCED.md](ADVANCED.md)) only one level deep.
• Forward Slashes: Always use / for paths, never \.
• Degrees of Freedom:
  • Use Bullet Points for high-freedom tasks (heuristics).
  • Use Code Blocks for medium-freedom (templates).
  • Use Specific Bash Commands for low-freedom (fragile operations).

4. Workflow & Feedback Loops

For complex tasks, include:

1. Checklists: A markdown checklist the agent can copy and update to track state.
2. Validation Loops: A "Plan-Validate-Execute" pattern. (e.g., Run a script to check a config file BEFORE applying changes).
3. Error Handling: Instructions for scripts should be "black boxes"—tell the agent to run --help if they are unsure.

5. Output Template

When asked to create a skill, output the result in this format:

[Folder Name]

Path: .agent/skills/[skill-name]/

[SKILL.md]

---