agentleFS
Sign inStart free
icarloscornejoicarloscornejo/doer/skills/setup/SKILL.md

setup

Skill0 starsChanged 5 days agoMITView on GitHub

Guided, one-time-per-scope configuration for the wk plugin. Invoke as "/wk:setup". Walks through locale (global, personal) and this project's Jira base URL + token env var name (per-project, optional), then verifies Jira access and offers an auto-detect fallback for the token env var name if none is loaded. Use "/wk:locale <code>" or "/wk:jira <url>" instead for a one-shot change to a single piece.

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 171 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:

    Run jira.sh config. Report {base_url, token_env}.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 171 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

/wk:setup - guided configuration

Three steps, each skippable. If run inside a git repo, run "${CLAUDE_PLUGIN_ROOT}/lib/helpers/workspace-guard.sh" acquire --no-lock first (steps 1-3 of lib/workspace-guard.md, not the per-ticket lock: this command is not ticket-scoped) so .doer/ is excluded before writing config.json.

Step 1. Locale (global)

AskUserQuestion: offer the current locale ("${CLAUDE_PLUGIN_ROOT}/lib/helpers/preferences.sh" get-locale), English, and a custom option. On an answer, run preferences.sh set-locale <code>. This applies to every project.

Step 2. Jira base URL (this project)

Plain-chat ask: "Jira base URL for this project? (e.g. https://jira.example.com, or 'skip')". On a URL, run "${CLAUDE_PLUGIN_ROOT}/lib/helpers/jira.sh" set-url <url>. On skip, leave unset: Jira stays optional for /wk:doer and required-but-deferred for /wk:bugfix.

Step 3. Jira token env var name (this project)

Only if step 2 was not skipped. Explain: the token is never written to disk, only the name of the env var that holds it. Default is JIRA_PAT. Plain-chat ask: "Does your token already live in a different env var (e.g. JIRA_PROD_PAT)? Name it, or say 'use JIRA_PAT'." On a custom name, run jira.sh set-token-env <name>.

Step 3.5. Atlassian Cloud auth (only if the URL matches *.atlassian.net)

Cloud rejects Bearer tokens (403 "Failed to parse Connect Session Auth Token"); it requires HTTP Basic with email:api_token. Plain-chat ask: "This looks like Atlassian Cloud. What email is your API token for? (from id.atlassian.com/manage-profile/security/api-tokens)". On an answer, run jira.sh set-auth-email <email>.

Step 4. Verify + auto-detect fallback

Run jira.sh config. Report {base_url, token_env}. If token_present: false, run the auto-detect pass:

"${CLAUDE_PLUGIN_ROOT}/lib/helpers/jira.sh" detect-token-env

Never print or persist the values, only the candidate NAMEs (this is all the helper ever prints). Also check the project memory for a previously-noted token env var name (never a secret value). If exactly one clear candidate turns up and it differs from the configured token_env, ask via AskUserQuestion whether to point jira_token_env at it. Otherwise, tell the user to export <TOKEN_ENV>="<their PAT>" in this shell (or their .zshrc / .envrc) and that re-running /wk:setup or any Jira-backed command will pick it up.

Close with one line: what got configured, what's still pending (if anything), and that /wk:bugfix and /wk:doer's auto-fetch are now ready.

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