Skip to content
Back to skills

Setup

ASecurity

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

  • 20 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
ai-agentsgit

Works with

  • cli
  • mcp

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned November 11, 2026

npx -y skills add helderberto/agent-skills --skill setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/helderberto-setup/badge)](https://www.skillsdirectory.com/skills/helderberto-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: setup
description: Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
disable-model-invocation: true
effort: low
argument-hint: '[local | github | jira <KEY>]'
---

# 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](issue-tracker-local.md). Done.

**GitHub / Jira** → copy the seed ([issue-tracker-github.md](issue-tracker-github.md) or [issue-tracker-jira.md](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>`.

Files in this skill

  • SKILL.md1.7 KB
  • issue-tracker-github.md807 B
  • issue-tracker-jira.md683 B
  • issue-tracker-local.md474 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.