findagent_create_package_draft
Create a DRAFT agent from an Agent Plugins package you wrote in this conversation: pass files as an object mapping each path to its TEXT (for example "skills/my-skill/SKILL.md", "skills/my-skill/references/guide.md", ".claude-plugin/plugin.json", "commands/review.md", "agents/reviewer.md"). FindAgent imports it exactly like an uploaded package — the same skill rules (at most 40 skills, valid Agent Skills names; too many is refused, never cut), the same caps (4 MB of text in total, 2 MB per file, 4000 files; the whole request, JSON escaping included, must also stay under the hosting platform's ~4.5 MB request limit), actions only where plugin.json declares them — stores it in your own namespace and saves a status=draft skills agent you own. Binary files cannot be sent. You must pass attestation: "own-work", confirming these are your own files. Then call findagent_submit_for_review in this client (price, originality and prohibited-content confirmations): the package is scanned and a person reviews it before anything is published. Listing fields are the same as findagent_create_draft (title, slug, tagline, description, category); the instructions, prompts and actions come from the files. NEVER put secret values in any file: an action's credentials are declared by name only. Which tool for which part: Instructions, Skills and Actions are authored as an Agent Plugins package and sent as files with findagent_create_package_draft; Code (a Node or Python program) uses findagent_create_code_draft from your own GitHub repo; an MCP server you already run uses findagent_create_remote_mcp; findagent_create_draft saves a declarative listing from findagent_import_repo grounding. Code part: start from https://github.com/FindAgent/agent-template (Node and Python variants). Building any part with an assistant: provider-neutral playbooks at https://github.com/FindAgent/agent-creators (start with AGENTS.md).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| llms | No | ||
| slug | Yes | Permanent kebab-case slug (3-60 chars). Check it with findagent_check_slug first. | |
| tags | No | ||
| files | Yes | The package: each key is a relative file path, each value the full text of that file. At least one SKILL.md (for example "skills/<name>/SKILL.md" with name + description frontmatter). | |
| title | Yes | Listing title (3-80 chars). | |
| tagline | Yes | One-line value proposition (10-140 chars). | |
| languages | No | ||
| attestation | Yes | Required: "own-work" — you confirm these files are your own work (or yours to publish). | |
| description | Yes | Listing description (50-4000 chars). | |
| tech_domains | No | ||
| category_slug | No | Primary category slug (see findagent_list_categories). | |
| example_prompts | No | Optional: up to 5 example prompts (more is refused, not cut). Omitted = the ones the package produced. | |
| additional_category_slugs | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | ||
| slug | No | ||
| title | No | ||
| status | No | ||
| account | No | ||
| created | No | ||
| left_out | No | ||
| next_tool | No | ||
| price_type | No | ||
| preview_url | No | ||
| skill_count | No | ||
| skill_notes | No | ||
| action_count | No | ||
| instructions | No | ||
| category_slug | No | ||
| slug_is_permanent_after_publish | No |