Agent skill

Maggy

Maggy is a local AI engineering command center. An agent skill from alinaqi/maggy.

MITAuto-check passedTesting & QA

Install Maggy

skills CLI

$ npx skills add alinaqi/maggy --skill maggy -a claude-code

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

GitHub CLI

$ gh skill install alinaqi/maggy maggy --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/alinaqi/maggy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/maggy .claude/skills/maggy && 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/

Paste into Claude Code

Install the "maggy" agent skill from https://github.com/alinaqi/maggy/tree/main/skills/maggy into .claude/skills/maggy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maggy", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/alinaqi/maggy/tree/main/skills/maggy

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add alinaqi/maggy --skill maggy -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install alinaqi/maggy maggy --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/maggy .agents/skills/maggy && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "maggy" agent skill from https://github.com/alinaqi/maggy/tree/main/skills/maggy into .agents/skills/maggy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maggy", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alinaqi/maggy --skill maggy -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install alinaqi/maggy maggy --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/maggy .cursor/skills/maggy && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "maggy" agent skill from https://github.com/alinaqi/maggy/tree/main/skills/maggy into .cursor/skills/maggy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maggy", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/alinaqi/maggy.git --path skills/maggy

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add alinaqi/maggy --skill maggy -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install alinaqi/maggy maggy --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/maggy .gemini/skills/maggy && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "maggy" agent skill from https://github.com/alinaqi/maggy/tree/main/skills/maggy into .gemini/skills/maggy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maggy", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install alinaqi/maggy maggy

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add alinaqi/maggy --skill maggy -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/maggy .github/skills/maggy && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "maggy" agent skill from https://github.com/alinaqi/maggy/tree/main/skills/maggy into .github/skills/maggy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maggy", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alinaqi/maggy --skill maggy -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install alinaqi/maggy maggy --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/maggy .opencode/skills/maggy && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "maggy" agent skill from https://github.com/alinaqi/maggy/tree/main/skills/maggy into .opencode/skills/maggy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maggy", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: maggy
GitHub stars: 707
Token cost: ~1.5k tokens
SKILL.md length: 512 words
Files: 1
Skills in repo: 71
Repo updated: Sep 24, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Maggy is a local AI engineering command center. An agent skill from alinaqi/maggy.

Works in 5 steps: Maggy queries the configured iCPG for… → Picks the right working directory based… → Spawns claude -p… → …
Tasks that involve Issue triage
SKILL.md covers When Maggy Helps, Install and Configure, Provider Abstraction and Execute Pipeline, plus 3 more sections
Calls claude, python3 and git; needs GITHUB_TOKEN and ANTHROPIC_API_KEY

What it does

Maggy is an agent skill from alinaqi/maggy. Maggy is a local AI engineering command center. AI-prioritized inbox across issue trackers (GitHub Issues/Asana), one-click TDD execute with iCPG context enrichment, daily competitor intelligence briefing.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Issue triage, Email management and Test-driven development. It works with GitHub and Asana. The repository describes itself as: What started as an opinionated Claude Code setup kit is now an autonomous AI engineering command center. The licence is MIT.

When your agent uses it

Tasks that involve Issue triage
Tasks that involve Email management
Tasks that involve Test-driven development

Example prompts

“/maggy”

Requirements

Python 3
A credential in GITHUB_TOKEN
A credential in ANTHROPIC_API_KEY

Workflow steps

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

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

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- claude
- python3
- git
- make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GITHUB_TOKEN
- ANTHROPIC_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Maggy loads about 1.5k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 512 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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 passed

The automated check found no risky patterns in SKILL.md.

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 alinaqi/maggy at commit 72a456e, republished under its MIT licence (© alinaqi). 512 words, ~1,482 tokens.

Download SKILL.mdSave it as .claude/skills/maggy/SKILL.md (or your agent's skills folder).

name: maggy
description: Maggy is a local AI engineering command center. AI-prioritized inbox across issue trackers (GitHub Issues/Asana), one-click TDD execute with iCPG context enrichment, daily competitor intelligence briefing.
when-to-use: When you want a persistent dashboard to triage tickets and spawn Claude Code runs against any repo
user-invocable: true
effort: medium

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

Scenario	How Maggy helps
Morning triage of 50 open issues	AI ranks them; top items stay top
Implementing a ticket	`Execute` → iCPG-enriched TDD pipeline
"What are competitors shipping?"	Daily briefing + filterable news feed
Multiple repos per team	Auto-picks right repo based on ticket content
New team onboarding	Configure via `/maggy-init`, no code writing

Install and Configure

bash

# 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.

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

Execute Pipeline

When you click Execute on a ticket:

Maggy queries the configured iCPG for relevant symbols, blast radius, and prior intents
Picks the right working directory based on ticket keywords + configured codebases
Spawns claude -p --dangerously-skip-permissions in that directory
Runs analyze → write failing tests → implement
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:

Configure competitors.categories: ["fintech", "embedded-finance"] in ~/.maggy/config.yaml
Click Discover — Claude identifies 12-18 competitors (market leaders, AI-first challengers, vertical specialists)
Maggy monitors their RSS blogs + Google News daily
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

Files

Just SKILL.md in skills/maggy of alinaqi/maggy.

Open the folder on GitHubat commit 72a456e

Compare with similar skills

Maggy 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.

Maggy compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Maggy this skillalinaqi/maggy	707	—	~1.5k	Automated safety check: Pass	MIT	17 days ago
GitHub Triageamd/gaia	1.6k	—	~2.3k	Automated safety check: Warn	MIT	yesterday
Triage IssueProgrammerAnthony/Anything-Extract	139	—	~504	Automated safety check: Pass	MIT	5 mo ago
Triage Issuesoftspark/ai-toolkit	179	—	~1.3k	Automated safety check: Notes	Apache-2.0	3 days ago
Openloomi Connectorsmelandlabs/openloomi	1k	—	~3.3k	Automated safety check: Pass	Apache-2.0	17 days ago
Setup Matt Pocock Skillsywwynm/EverythingDone	144	8 repos	~1.7k	Automated safety check: Pass	GPL-3.0	2 days ago

Similar skills

GitHub Triage
amd/gaia
Triage GitHub work with the gh CLI — your unread notification inbox, or one repository's issue backlog.
1.6k GitHub stars~2.3k tokensUpdated yesterday
DevelopmentAuto-check: warnings
Triage Issue
ProgrammerAnthony/Anything-Extract
通过探索代码库对 Bug/Issue 进行排查归因，并基于 TDD 方式生成修复计划，同时创建对应的 GitHub issue。适用于用户报告了 bug、希望创建 issue、提到“triage”，或想调查并规划某个问题的修复方案。
139 GitHub stars~504 tokensUpdated 5 mo ago
DevelopmentAuto-check passed
Triage Issue
softspark/ai-toolkit
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.
179 GitHub stars~1.3k tokensUpdated 3 days ago
DevelopmentAuto-check: notes
Openloomi Connectors
melandlabs/openloomi
openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…
1k GitHub stars~3.3k tokensUpdated 17 days ago
Productivity & AutomationAuto-check passed
Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
144 GitHub starsUsed in 8 repos~1.7k tokens
Agent WorkflowsAuto-check passed
Setup Matt Pocock Skills
yamcodes/arkenv
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
147 GitHub stars~1.8k tokensUpdated yesterday
Agent WorkflowsAuto-check passed

Questions about Maggy

What does Maggy do?

Maggy is a local AI engineering command center. An agent skill from alinaqi/maggy. Maggy is an agent skill from alinaqi/maggy. Maggy is a local AI engineering command center.

When should I use Maggy?

Maggy fits situations like: tasks that involve Issue triage; tasks that involve Email management; tasks that involve Test-driven development.

How do I install Maggy in Claude Code?

Run `npx skills add alinaqi/maggy --skill maggy -a claude-code`. Or copy the skill folder (skills/maggy in alinaqi/maggy) into .claude/skills/maggy in your project. Claude Code loads it when a task matches its description.

How do I install Maggy in Codex?

Run `npx skills add alinaqi/maggy --skill maggy -a codex`. Or copy the skill folder (skills/maggy in alinaqi/maggy) into .agents/skills/maggy in your project. Codex loads it when a task matches its description.

Can I use Maggy 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 alinaqi/maggy --skill maggy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maggy, .gemini/skills/maggy, .github/skills/maggy and .opencode/skills/maggy in your project.

What does Maggy need to run?

Going by SKILL.md and its folder, Maggy needs the command-line tools its instructions call (claude, python3, git and make) and credentials named GITHUB_TOKEN and ANTHROPIC_API_KEY. Our summary lists: Python 3; A credential in GITHUB_TOKEN; A credential in ANTHROPIC_API_KEY.

Does Maggy access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Maggy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Maggy use?

Maggy 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 Maggy use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Maggy?

Skills that share tags, products or a category with Maggy: GitHub Triage (amd/gaia, 1.6k stars), Triage Issue (ProgrammerAnthony/Anything-Extract, 139 stars), Triage Issue (softspark/ai-toolkit, 179 stars) and Openloomi Connectors (melandlabs/openloomi, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Maggy?

alinaqi (a GitHub user) maintains it in alinaqi/maggy, which has 707 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on September 24, 2026.

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

Install Maggy

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Maggy Skill

⚠️ Execute permission model (important)

When Maggy Helps

Install and Configure

Provider Abstraction

Execute Pipeline

Competitor Intelligence

Not Included

Files

Files

Compare with similar skills

Similar skills

More from alinaqi/maggy

Related

Questions about Maggy