Setting the file. One moment.
Skill 29 · Firecrawl Workflows
Subchapter 29.1
references/workflow-authoring.mdMarkdown2 KBView on GitHub
Use this reference when adding or reviewing workflow skills.
Use:
Avoid:
Do not run a long interview by default. First infer from the user’s message, files, URLs, and surrounding context. If the agent can safely start, start.
Ask at most 1-3 concise clarifying questions only when a required input is missing or ambiguity would materially change the work. Prefer defaults for non-blocking choices and state them briefly.
For recurring jobs, each workflow should be expressible as:
workflow: skill-name
cadence: weekly
inputs:
subject: example
urls: []
competitors: []
output: report.mdThe skill does not need to implement a scheduler. It should make the inputs and outputs stable enough for another system to schedule it.
anthropics/skills: use simple skill directories and minimal metadata.anthropics/financial-services: borrow outcome orientation and optional agent packaging ideas.anthropics/claude-for-legal: borrow vertical workflow organization and concrete deliverable framing.Do not copy heavier managed-agent scaffolding unless this repo starts shipping standalone hosted agents.