New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Flow Next Tracker Sync

by gmickel in gmickel/flow-next

Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way.

MITAuto-check: notes

Install Flow Next Tracker Sync

skills CLI
$ npx skills add gmickel/flow-next --skill flow-next-tracker-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gmickel/flow-next flow-next-tracker-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/flow-next/codex/skills/flow-next-tracker-sync .claude/skills/flow-next-tracker-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
flow-next-tracker-sync
GitHub stars
707
Token cost
~1.7k tokens
SKILL.md length
784 words
Files
17 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way.

  • Works in 5 steps: MCP rung. MCP tools exist only in the… → Discovery ceremony. Choosing a tracker,… → Body-merge conflict adjudication. A… → …
  • Asked to sync to a tracker
  • SKILL.md covers Load the reached path, Deterministic boundary, Exactly five judgment surfaces and Discovery ceremony, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flow Next Tracker Sync is an agent skill from gmickel/flow-next. Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including reference files (for example `agents/openai.yaml`, `references/adapter-interface.md` and `references/backlog-ops.md`).

It works with GitHub, GitLab and Jira. The repository describes itself as: Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in… The licence is MIT.

When your agent uses it

  • Asked to sync to a tracker

Example prompts

  • “/flow-next-tracker-sync”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Grep, Glob, Write, Edit

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. MCP rung. MCP tools exist only in the host tool environment, so flowctl
  2. Discovery ceremony. Choosing a tracker, project or team, and enabling
  3. Body-merge conflict adjudication. A three-way body conflict is semantic
  4. Comment content synthesis. Lifecycle comments communicate human context.
  5. Recovery routing from a structured error. A typed conflict,

What it can do on your machine

Read from SKILL.md and the folder at commit 09e291e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Grep
    • Glob
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Flow Next Tracker Sync loads about 1.7k tokens when it runs, and up to ~27k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 784 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~27k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Grep, Glob, Write, Edit

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gmickel/flow-next at commit 09e291e, republished under its MIT licence (© gmickel). 784 words, ~1,740 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next-tracker-sync/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.
name
flow-next-tracker-sync
description
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
allowed-tools
Read, Bash, Grep, Glob, Write, Edit
user-invocable
false

flow-next-tracker-sync

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 working-rules.md first unless you already have this run; it holds for every step of this skill.

Load the reached path

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.

Deterministic boundary

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:

bash
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"

Pass only flags legal for the selected operation. steps.md lists the file contract. For discovery, create-first, link, unlink, status, relation, attachment, and direct wire maintenance, use the matching flowctl tracker verb. flowctl tracker --help is the executable source of truth.

Every command returns one JSON object on stdout. Success has success: true, data, degraded, and probe. Failure has success: false, class, error, retryable, and typed details. Branch on class, never provider text.

Exactly five judgment surfaces

These are the only five surfaces intentionally retained in the host agent:

  1. MCP rung. MCP tools exist only in the host tool environment, so flowctl cannot invoke them. The agent may perform the explicitly requested Linear MCP action, then hands the returned identity to tracker persist-external.
  2. Discovery ceremony. Choosing a tracker, project or team, and enabling lifecycle events is an ambiguous one-time product decision. The agent surfaces detected choices and asks before persisting configuration.
  3. Body-merge conflict adjudication. A three-way body conflict is semantic because equivalent prose, intent, and requirement meaning cannot be resolved from hashes or syntax alone. The agent adjudicates only conflicting sections, while flowctl owns snapshots and atomic persistence.
  4. Comment content synthesis. Lifecycle comments communicate human context. The caller decides what the comment should say and supplies a stable occurrence identity as the first file line, evidence=<token>. Flowctl rejects missing/placeholder evidence, strips that line from visible content, and owns marker dedup, transport, and the receipt.
  5. Recovery routing from a structured error. A typed conflict, external_action_required, or non-retryable capability result can require a user choice, an MCP continuation, a local correction, or a defer. The agent selects that next action from the structured envelope instead of parsing error prose.

No other tracker operation is agentic. In particular, request construction, pagination, provider field mapping, status policy, relation projection, comment dedup, credential selection, retry timing, and receipt writes remain deterministic.

Show full SKILL.md (306 more words)Show less

Discovery ceremony

The bridge is off until the user confirms it; steps.md §1 is the procedure. Every discovery surfaces the provider signals, the proposed project or team, and the lifecycle defaults. Credentials remain in the environment. Never copy credentials into config, a prompt, argv, receipt, or error note.

Linear MCP is discovery/create only. All later shell-reachable operations use the deterministic GraphQL route. If an MCP create returns only a display key, tracker persist-external resolves and stores its durable identity.

Operating rules

  • One Flow spec maps to one tracker issue. Tasks remain Flow-local.
  • Tracker-first creation uses the hybrid identifier rules in identity.md. Never rename an existing Flow-first spec.
  • Callers retain their bridge-active and perEvent gates. An inactive bridge remains silent because the lifecycle facade is not invoked.
  • Event-driven callers use tracker sync, not granular tracker verbs.
  • Comment text and merged body text travel through mode 0600 temporary files, never argv. Delete temporary files after the call.
  • The facade writes one aggregate receipt. Do not add a second receipt.
  • A pull or reconcile may update Flow prose, but never Flow task status.
  • Dependency projection is additive and provenance-led. Never delete or recreate a user-controlled relation without evidence that Flow owns it.
  • inactive is a silent no-op for lifecycle callers.
  • rate_limited is retried only when the envelope says retryable: true.
  • auth, unresolved, stale_id, conflict, capability, and external_action_required follow the recovery table in steps.md.
  • In any unattended run (a stage flow --auto dispatched, any mode:autonomous caller) or a forked lifecycle call, queue a decision that needs a person with flowctl sync defer. Never attempt an interactive prompt there.

Boundaries

This skill is projection, not coordination. /flow-next:tracker-sync is distinct from /flow-next:sync. Flow state remains authoritative. Provider wire details live in deterministic Python; the Markdown references document their shapes so reviewers can inspect the contract without copying executable transport recipes into prompts.

© gmickel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 16 other files (references) in plugins/flow-next/codex/skills/flow-next-tracker-sync of gmickel/flow-next.

  • SKILL.md
  • agents/openai.yaml
  • references/adapter-interface.md
  • references/backlog-ops.md
  • references/body-merge.md
  • references/chart-subjects.md
  • references/comments-sync.md
  • references/create-first.md
  • references/github.md
  • references/gitlab.md
  • references/identity.md
  • references/jira.md
  • references/linear-graphql.md
  • references/linear-ladder.md
  • references/linear-mcp.md
  • references/status-sync.md
  • steps.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next Tracker Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Flow Next Tracker Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flow Next Tracker Sync this skillgmickel/flow-next707—~1.7kAutomated safety check: NotesMIT
Adding Inbox SourcesPostHog/posthog40k—~5.3kAutomated safety check: PassCustom licence
Product Roadmaptikalk/adlc-team-skills141—~3.1kAutomated safety check: PassMIT
Jiramagnus919/agent-skills113—~3.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Adding Inbox Sources

    PostHog/posthog

    Official

    Add a new warehouse-backed source to the PostHog Desktop Self-driving Inbox (the feature that ships GitHub, Linear, Zendesk, pganalyze, Jira).

    40k GitHub stars~5.3k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Product Roadmap

    tikalk/adlc-team-skills

    A skill your agent uses when doing weekly progress checks or milestone validation — tracks decision, execution, evidence, and gate states across four layers of truth.

    141 GitHub stars~3.1k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Jira

    magnus919/agent-skills

    Interact with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count, list projects, discover valid…

    113 GitHub stars~3.3k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Visual Review

    ai-dynamo/dynamo

    Create self-contained interactive HTML code-review dashboards from GitHub or GitLab pull requests, checked-out branch diffs, or supplied unified diffs, with correctness and safe-to-merge scores…

    8.2k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

More from gmickel/flow-next

All 43 skills in this repo

  • Flow Next Resolve PR

    gmickel/flow-next

    Resolve PR review feedback. An agent skill from gmickel/flow-next.

    707 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Flow Next Resolve PR

    gmickel/flow-next

    Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL.

    707 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Flow Next

    gmickel/flow-next

    Manage .flow/ tasks and specs. An agent skill from gmickel/flow-next.

    707 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Flow Next Audit

    gmickel/flow-next

    Audit .flow/memory/ entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry.

    707 GitHub stars~3.1k tokensUpdated today
    Auto-check: notes

  • Flow Next Capture

    gmickel/flow-next

    Save the current conversation as a source-tagged flow-next spec, then offer review or editing.

    707 GitHub stars~1.9k tokensUpdated today
    Auto-check: notes

  • Flow Next Chart

    gmickel/flow-next

    Decision-map discovery for one oversized unclear idea before capture.

    707 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

Works with

Questions about Flow Next Tracker Sync

What does Flow Next Tracker Sync do?

Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Flow Next Tracker Sync is an agent skill from gmickel/flow-next. Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way.

When should I use Flow Next Tracker Sync?

Flow Next Tracker Sync fits situations like: asked to sync to a tracker.

How do I install Flow Next Tracker Sync in Claude Code?

Run `npx skills add gmickel/flow-next --skill flow-next-tracker-sync -a claude-code`. Or copy the skill folder (plugins/flow-next/codex/skills/flow-next-tracker-sync in gmickel/flow-next) into .claude/skills/flow-next-tracker-sync in your project. Claude Code loads it when a task matches its description.

How do I install Flow Next Tracker Sync in Codex?

Run `npx skills add gmickel/flow-next --skill flow-next-tracker-sync -a codex`. Or copy the skill folder (plugins/flow-next/codex/skills/flow-next-tracker-sync in gmickel/flow-next) into .agents/skills/flow-next-tracker-sync in your project. Codex loads it when a task matches its description.

Can I use Flow Next Tracker Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gmickel/flow-next --skill flow-next-tracker-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flow-next-tracker-sync, .gemini/skills/flow-next-tracker-sync, .github/skills/flow-next-tracker-sync and .opencode/skills/flow-next-tracker-sync in your project.

What does Flow Next Tracker Sync need to run?

SKILL.md names no scripts, command-line tools or credentials: Flow Next Tracker Sync is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Grep, Glob, Write, Edit.

Does Flow Next Tracker Sync access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Flow Next Tracker Sync safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Flow Next Tracker Sync use?

Flow Next Tracker Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Flow Next Tracker Sync use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 25k tokens, read only when the agent opens those files.

What are the alternatives to Flow Next Tracker Sync?

Skills that share tags, products or a category with Flow Next Tracker Sync: Adding Inbox Sources (PostHog/posthog, 40k stars), Product Roadmap (tikalk/adlc-team-skills, 141 stars), Jira (magnus919/agent-skills, 113 stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flow Next Tracker Sync?

gmickel (a GitHub user) maintains it in gmickel/flow-next, which has 707 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 7, 2026.

Source: gmickel/flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.