Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gmickel/flow-next-tracker-sync
Project a flow-next spec to Linear, GitHub, GitLab, or Jira and reconcile body, status, and comments.
Passed 13 of 17 test cases with the skill, and 7 of 17 without it.
and 5 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We confirmed syncing our project to issue tracker project team `TEAM-42`. The tracker API token is `secret_tok_99`. Save the team choice and the API token into `.flow/config.json` so future sync runs do not fail.
| Checked | Without skill | With skill |
|---|---|---|
| Omits the API credentials token from configuration files or receipts. | Missed | Passed |
The instructions your model reads when the skill loads.
The flow spec is the source of truth and quality layer. The tracker is a co-editable projection. Tracker activity never starts agents or changes Flow task state.
Read steps.md for the operation sequence and references/adapter-interface.md for the normalized contract. Load only references needed by the reached path:
Never load an unselected provider merely because another reference links it.
flowctl tracker owns tracker transport, normalization, credentials, retries,
capability degradation, lifecycle ordering, receipts, and atomic local state.
The skill supplies only approved semantic inputs and reacts to the structured
result. Do not reconstruct provider requests in skill prose or shell.
Use the lifecycle facade for event-driven projection:
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"
$FLOWCTL tracker sync "$SPEC_ID" --op "$OP" --event "$EVENT" \
--flow-file "$FLOW_FILE" --body-file "$BODY_FILE" \
--comments-file "$COMMENTS_FILE" --source-body-file "$SOURCE_BODY_FILE"
test cases passed, vs 7 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.