Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alinaqi avatar

Maggy

  • 93 installs
  • 706 repo stars
  • Updated July 14, 2026
  • alinaqi/claude-bootstrap

maggy is a Claude skill and local dashboard that prioritizes engineering tickets and spawns Claude Code runs to implement them.

About

maggy is a local AI engineering command center that triages tickets and spawns Claude Code runs against any repo. It ranks open issues by urgency, OKR alignment, and recency, offers one-click Execute that launches Claude Code with iCPG context injected to run a TDD pipeline, and generates a daily competitor intelligence briefing. A developer uses it as a persistent dashboard for morning triage and ticket implementation across multiple repos and issue trackers.

  • AI-prioritized inbox across GitHub Issues, Asana, and Linear providers
  • One-click Execute spawns Claude Code with iCPG context injected
  • Daily competitor intelligence briefing from RSS and Google News

Maggy by the numbers

  • 93 all-time installs (skills.sh)
  • Ranked #1,396 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

maggy capabilities & compatibility

Requires a GITHUB_TOKEN and an ANTHROPIC_API_KEY set as environment variables

Capabilities
project management · planning · orchestration
Works with
github · jira
Use cases
project management · planning · orchestration
Pricing
Bring your own API key
From the docs

What maggy says it does

**Maggy** is a generic, local AI engineering command center. Install once, point it at your team's issue tracker and codebases
SKILL.md
**AI-prioritized inbox** — ranks open issues by urgency, OKR alignment, and recency
SKILL.md
**One-click Execute** — spawns Claude Code locally with iCPG context injected
SKILL.md
npx skills add https://github.com/alinaqi/claude-bootstrap --skill maggy

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs93
repo stars706
Last updatedJuly 14, 2026
Repositoryalinaqi/claude-bootstrap

What it does

Triage issue-tracker tickets in an AI-prioritized inbox and spawn a Claude Code run to implement one.

Who is it for?

Prioritizing open issues and one-click implementing tickets across GitHub and Asana on repos you own

Skip if: Running against repos or tickets you do not trust, since Execute runs Claude with dangerously-skip-permissions

When should I use this skill?

You want a persistent dashboard to triage tickets and spawn Claude Code runs against any repo

What you get

A ranked inbox plus one-click, context-enriched Claude Code runs that implement tickets

  • a ranked issue inbox
  • spawned TDD Claude Code sessions
  • a daily competitor briefing

By the numbers

  • Discover identifies 12-18 competitors
  • Three issue-tracker providers: GitHub, Asana, Linear stub

Files

SKILL.mdMarkdownGitHub ↗

Maggy Skill

Maggy is a generic, local AI engineering command center. Install once, point it at your team's issue tracker and codebases, and get:

  • AI-prioritized inbox — ranks open issues by urgency, OKR alignment, and recency
  • One-click Execute — spawns Claude Code locally with iCPG context injected
  • Competitor intelligence — daily AI briefing on your competitive landscape
  • No hardcoding — works for any team, any stack, any issue tracker

⚠️ Execute permission model (important)

Execute currently runs claude -p --dangerously-skip-permissions so the TDD pipeline isn't blocked waiting on approval prompts (subprocess has no terminal). That flag grants Claude full permission to write/edit files and run shell commands inside the target codebase, and the prompt it receives includes content from the issue tracker (which any team member can author).

Hardening already in place:

  • working_dir is validated against the list of codebase roots in

~/.maggy/config.yaml — Claude can't be pointed at arbitrary filesystem paths.

  • Only tickets from your configured trackers reach Execute; no public-internet

input flows into the prompt.

Roadmap: move the unconditional flag behind per-codebase config (auto_approve: true|false) so privileged execution becomes opt-in. Until then, treat Execute like git pull && make on any ticket you push the button for — only run it on repos you own, against tickets from authors you trust.

┌──────────────────────────────────────────────────────────────┐
│  maggy               ──────────────┐                          │
│  ├── skills/         ← installed globally → ~/.claude/       │
│  ├── commands/       ← installed globally → ~/.claude/       │
│  ├── scripts/icpg/   ← used by Maggy for context enrichment  │
│  └── maggy/          ← dashboard: run `./install.sh` to use  │
│      ├── src/                                                │
│      │   ├── providers/   ← GitHub / Asana / Linear          │
│      │   ├── services/    ← inbox, competitor, executor      │
│      │   └── api/         ← FastAPI routes                   │
│      └── install.sh                                          │
└──────────────────────────────────────────────────────────────┘

---

When Maggy Helps

ScenarioHow Maggy helps
Morning triage of 50 open issuesAI ranks them; top items stay top
Implementing a ticketExecute → iCPG-enriched TDD pipeline
"What are competitors shipping?"Daily briefing + filterable news feed
Multiple repos per teamAuto-picks right repo based on ticket content
New team onboardingConfigure via /maggy-init, no code writing

---

Install and Configure

# One-time install
cd $(cat ~/.claude/.bootstrap-dir)/maggy
./install.sh

# Configure
# Edit ~/.maggy/config.yaml — see maggy/config.example.yaml for the schema

# Credentials
export GITHUB_TOKEN=ghp_...
export ANTHROPIC_API_KEY=sk-ant-...

# Run
python3 -m src.main

# Or from Claude Code:
#   /maggy-init    # interactive wizard
#   /maggy         # launch dashboard

---

Provider Abstraction

Maggy services never see GitHub/Asana directly — they talk to an IssueTrackerProvider Protocol. Drop-in swap between:

  • GitHubIssuesProvider — scans multiple repos, aggregates open issues, maps "done" → closed
  • AsanaProvider — queries projects, respects workspace scope
  • LinearProvider — stub for future

The same inbox, Execute pipeline, and Competitor features work with any provider.

---

Execute Pipeline

When you click Execute on a ticket:

1. Maggy queries the configured iCPG for relevant symbols, blast radius, and prior intents 2. Picks the right working directory based on ticket keywords + configured codebases 3. Spawns claude -p --dangerously-skip-permissions in that directory 4. Runs analyze → write failing tests → implement 5. Captures output in a session you can follow in the Sessions tab

Because the spawned Claude Code runs in the target repo, it picks up:

  • That repo's CLAUDE.md
  • Your global ~/.claude/CLAUDE.md
  • All bootstrap skills
  • .claude/hooks/, .mcp.json

So Execute gets the full bootstrap experience — not a stripped-down version.

---

Competitor Intelligence

Generic — works for any domain:

1. Configure competitors.categories: ["fintech", "embedded-finance"] in ~/.maggy/config.yaml 2. Click Discover — Claude identifies 12-18 competitors (market leaders, AI-first challengers, vertical specialists) 3. Maggy monitors their RSS blogs + Google News daily 4. Daily briefing is generated once per day (cached), regeneratable on demand

---

Not Included

Maggy MVP is focused. Not shipped:

  • Meeting bot (voice)
  • Slack integration
  • P2P network + session handoff
  • Self-improvement (/improve-maggy)
  • Linear provider (stub only)

These are v2 work.

---

Files

  • maggy/PLAN.md — architecture rationale
  • maggy/README.md — user docs
  • maggy/src/providers/base.py — IssueTrackerProvider Protocol
  • maggy/src/services/executor.py — TDD pipeline
  • maggy/src/services/competitor.py — discovery + briefing
  • maggy/src/services/inbox.py — AI prioritization
  • commands/maggy.md/maggy launcher
  • commands/maggy-init.md/maggy-init setup wizard

Related skills

FAQ

What issue trackers does maggy support?

It supports GitHub Issues and Asana providers, with a Linear provider as a stub, all behind an IssueTrackerProvider protocol.

How does Execute run code?

Execute spawns claude -p with dangerously-skip-permissions in a validated codebase root, so run it only on repos you own and tickets you trust.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.