agentleFS
Sign inStart free
helderbertohelderberto/agent-skills/skills/setup/SKILL.md

setup

Skill19 starsChanged 32 days agoMITView on GitHub

Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never touch committed files: no AGENTS.md, CLAUDE.md, or .gitignore edits.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup

Per repo. Records where every flow skill keeps specs and tickets. No config → markdown under .specs/, the default. GitHub or Jira → only in that tracker. Rerun to switch: new work follows the new choice, nothing migrates.

1. Explore

  • git remote -v: GitHub remote?
  • .specs/issue-tracker.md: prior output of this skill?
  • git check-ignore -q .specs: already ignored?

2. Ask one question

Argument given (local, github, jira <KEY>) → skip the question. Otherwise: which tracker? Lead with the recommendation: GitHub when the remote is on GitHub, else local.

  • GitHub → gh CLI
  • Jira → ask the project key; Atlassian MCP
  • Local → markdown in .specs/ only

3. Write

Never touch committed files: no AGENTS.md, CLAUDE.md, or .gitignore edits. The skills read the config directly.

Local → remove .specs/issue-tracker.md if present; skills fall back to issue-tracker-local.md. Done.

GitHub / Jira → copy the seed (issue-tracker-github.md or issue-tracker-jira.md) to .specs/issue-tracker.md, filling the placeholders.

.specs/ not ignored → append .specs/ to .git/info/exclude: ignored for this clone, never committed.

GitHub + hitl label missing → gh label create hitl --force.

4. Done

Print the tracker chosen and the files written. Switching later: rerun, or edit .specs/issue-tracker.md.

Next: /hb:triage or /hb:grill <idea>.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free