Author Flowglad Skill

Create a durable Flowglad Skill package and follow its immutable revision lifecycle.

Authoring process

1. Gather the reusable behavior, inputs, outputs, failure conditions, and representative synthetic cases.
2. Use skills.list and skills.get when Flowglad MCP is available. Prefer a suitable active Skill over creating a duplicate.
3. For a new Skill, derive the slug from the request. For an update, resolve the exact Skill and base revision; never infer identities from names.
4. Read references/PACKAGE_CONTRACT.md completely.
5. Copy assets/starter-package, rename SKILL.template.md to exactly SKILL.md, replace every placeholder, and extend only what the capability needs.
6. For every selected Python function, read references/OWS_COMPATIBILITY.md and use the OWS code ABI. Do not add a CLI wrapper around OWS code.
7. Create or revise SKILL.md, support files, scripts/**.py, and small flowglad-ows-code-test-v1 cases under tests/**.json. Keep scratch work outside the package.
8. Run Python syntax checks and any available Flowglad OWS verifier. Do not execute the selected function as a positional-argument CLI.
9. Run this skill's bundled helper as python3 /path/to/author-flowglad-skill/scripts/build-package-payload.py PACKAGE_DIR for inline MCP preflight. For large packages or MCP byte-transport failures, add --transport staged and follow references/MCP_LIFECYCLE.md.
10. Submit only when the user explicitly asks to create, upload, publish, or update the remote Skill.
11. Poll skills.get_lifecycle_request, then skills.get until the candidate reaches its final verification state. Repair rejected authored bytes as a new immutable candidate.

Package design