Short answer: Drop the "Anthropic → Create Skill" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Display Name display_name | string | Required | Human-friendly name shown in the Claude.ai UI and returned in API responses. |
SKILL.md URL skill_file_url | string | Required | Public HTTPS URL of the SKILL.md file describing this skill. The executor fetches the URL and uploads its bytes as the skill's primary file. For multi-file skills (with scripts/references), upload a tarball or use the Files API + Skills API directly. |
{"display_name": "e.g. Code Reviewer","skill_file_url": "e.g. https://example.com/skills/code-reviewer/SKILL.md"}
{"id": "skill_abc123","created_at": "2026-05-13T14:00:00Z","display_name": "Code Reviewer"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.