ShipfoxHQ/shipfox / libs/shared/workflow/templates/assets/skills/create-workflow-from-template
create-workflow-from-template
VerifiedUse when setting up a Shipfox workflow from a template.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| references/ask-options.md | markdown | 2.2 KB |
| references/choose-models.md | markdown | 1.6 KB |
| references/confirm-named-template.md | markdown | 1.7 KB |
| references/deliver-to-hosted-project.md | markdown | 1.7 KB |
references/deliver-to-hosted-project.md
View on GitHub# Deliver to a Shipfox-hosted project
Use this procedure in place of steps 7 to 9 of `skill://shipfox/create-workflow-from-template/SKILL.md` when the selected project has a null `source_connection`. Shipfox hosts its config in a repository you write to by branch. You commit to a branch, test the branch, and stop.
1. Choose a branch such as `shipfox/add-<template>`. Call `commit_config_changes` with that branch, no `expected_head`, a short `message`, and one change: the validated YAML at `.shipfox/workflows/<descriptive name>.yml`, with the template marker. Keep setup commands inline. If the tool returns `repository-read-only`, the config lives in a linked repository: follow steps 7 to 9 of the skill and ignore the pointer to this file at the top of step 7.
2. If step 6 ended with no event for an integration trigger, do not run. Report "shape validated, not executed" and go to step 4.
3. Follow `skill://shipfox/test-workflow-change/SKILL.md`, but call `create_dev_run` with `ref` set to the branch, `commit` set to the commit the last call returned, `config_path` set to the committed file, and no `content`. Share the `run_url`; if absent, share `run_id` and say no UI link was returned. To change the file after a failed run, read it with `read_config_file` at the branch, then commit again with that commit as `expected_head`. On `stale-head`, read the files at `details.head` and retry.
4. In your final message, name the branch. If you ran it, share the run link and say the workflow is tested on the branch; if step 2 skipped the run, say "shape validated, not executed" and share no link. Say it is not live yet, because a person has to approve the branch before it reaches the default branch. Never suggest a pull request, and never ask the user to open one.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |