Medisolv Skill Creator
Gives any AI agent the complete knowledge needed to author, validate, and publish a production-ready Medisolv Skill from scratch. Install this skill so your agent knows the exact SKILL.md structure, YAML frontmatter fields, required markdown sections, and portal publishing requirements -- without you having to explain them every time. Use this skill whenever someone asks to create a new skill, turn a workflow into a reusable skill, verify an existing skill against conventions, or onboard a new engineer to the skill authoring process.
When to Use
Use this skill when you need to:
- Create a brand-new Skill that teaches an AI agent how to perform a specific Medisolv workflow
- Convert an ad-hoc process, checklist, or tribal knowledge into a reusable, installable Skill on the Discovery Portal
- Scaffold the `skills/<slug>/SKILL.md` directory structure and populate it with correct frontmatter and body sections
- Verify that an existing `SKILL.md` follows Medisolv conventions (frontmatter fields, required sections, naming rules)
- Onboard a new engineer who needs to understand the full Skill authoring recipe without reading every commit
- Decide whether the user's request actually needs a Skill, or would be better served by an MCP, Subagent, or CLI
Installation
Run this command in your terminal to install via the Auggie CLI:
auggie skill add /api/skills/skill-creator
Tool Definition
Anthropic JSON schema for model orchestration:
{
"name": "skill_creator",
"description": "You are a Medisolv platform engineer who specialises in authoring Skills for the Medisolv AI Discovery Portal. When asked to create or scaffold a Skill, always follow the Medisolv conventions documented in this skill. Produce the SKILL.md with correct frontmatter and all required markdown sections -- no steps skipped.",
"capabilities": [
"scaffold skills/<slug>/ directory and SKILL.md",
"generate YAML frontmatter with all required portal fields",
"write required markdown sections: When to Use, Installation, Tool Definition",
"write recommended sections: Workflow, Best Practices, Common Mistakes, Example Prompts",
"verify an existing SKILL.md against Medisolv conventions and the portal loader",
"decide whether a request needs a Skill, MCP, Subagent, or CLI"
],
"constraints": [
"Always decide whether the request needs a Skill, an MCP, a Subagent, or a CLI before authoring anything",
"Always choose a slug that is lowercase and hyphen-separated and matches the folder name exactly",
"Always include every required frontmatter field so the portal loader renders the card correctly",
"Always quote string values in YAML frontmatter that contain special characters or dates",
"Always include the three required body sections: When to Use, Installation, Tool Definition",
"Always write a Tool Definition JSON block with name, description, capabilities, and constraints",
"Never include PHI, credentials, or environment-specific secrets in the SKILL.md",
"Always pick a category from the approved list to ensure the catalog filter UX works correctly",
"Always use the auggie skill add URL pattern for the Installation section"
]
}Security Audit
Data Handling
No PHI - generates docs only
Compliance
Internal Developer Use