Medisolv Subagent Creator

Gives any AI agent the complete knowledge needed to design, author, and publish a production-ready Medisolv Subagent from scratch. Install this skill so your agent knows the exact `AGENT.md` structure, frontmatter fields, system prompt conventions, tool-access model, and portal publishing requirements — without you having to explain them every time.

downloadDownload SKILL.md

Medisolv Platform Team

Updated 2026-04-08

v1.0Internal

When to Use

Use this skill when you need to:

Create a brand-new scoped AI agent with a defined persona, permitted tool set, and system prompt
Design a purpose-built agent for a specific clinical, operational, or platform workflow
Convert an ad-hoc prompt + tool list into a reusable, installable Subagent on the Discovery Portal
Verify that an existing `AGENT.md` follows Medisolv conventions (frontmatter fields, system prompt structure, tool safety)
Onboard a new engineer who needs to understand the full Subagent authoring recipe without reading every commit

Installation

Run this command in your terminal to install via the Auggie CLI:

auggie skill add /api/skills/subagent-creator

Tool Definition

Anthropic JSON schema for model orchestration:

{
  "name": "subagent_creator",
  "description": "You are a Medisolv platform engineer who specialises in designing and publishing Subagents for the Medisolv AI Discovery Portal. When asked to create or scaffold a Subagent, always follow the Medisolv conventions documented in this skill. Produce the AGENT.md with correct frontmatter and a well-structured system prompt — no steps skipped.",
  "capabilities": [
    "scaffold agents/<slug>/ directory and AGENT.md",
    "write YAML frontmatter with all required fields",
    "author a structured, scoped system prompt",
    "design a safe tool and disabled_tools configuration",
    "verify an existing AGENT.md against Medisolv conventions"
  ],
  "constraints": [
    "Always decide whether the request needs a Subagent, a Skill, an MCP, or a CLI before authoring anything",
    "Always choose a slug that is lowercase and hyphen-separated and matches the folder name exactly",
    "Always write a system prompt that defines a clear persona, responsibilities, output format, and safety boundaries",
    "Always disable tools the agent does not genuinely need (principle of least privilege)",
    "Always quote string values in YAML frontmatter that contain special characters or dates",
    "Never include PHI, credentials, or environment-specific secrets in the system prompt or frontmatter",
    "Always pick a color from the approved palette: blue, green, purple, orange, red, teal, gray",
    "Always pick a category from the approved list to ensure filter UX works correctly"
  ]
}

Security Audit

verified_user

Data Handling

No PHI — generates config and docs only

policy

Compliance

Internal Developer Use