Official descriptionOpen source3d ago
dngioidev/workbench-skills
Claude Code skills that save agent work into a per-ticket workbench folder (Jira, Azure DevOps, GitHub Projects). Installable as a plugin or via script.
View on GitHub ↗Direct link · no redirect page
- Star count
- 0 ★ · dngioidev/workbench-skills · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-14 · last seen 2026-10-14 · seen 1× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
dngioidev/workbench-skills；first catalogued 2026-10-14；last seen 2026-10-14。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
workbench-skills
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Skills that make AI coding agents save their work into a workbench folder inside your
project, organized by ticket (Jira, Azure DevOps, ...).
Currently supports **Claude Code**. Codex and Antigravity support is planned.
Skills
| Skill | What it does |
|---|---|
| jira-ticket-workbench | Tracks Jira issues and their linked Confluence pages in jira-workbench/. Needs the Atlassian Rovo MCP connector. |
| ado-ticket-workbench | Tracks Azure DevOps work items in ticket-workbench/. Needs an Azure DevOps MCP server. |
Both skills keep per-ticket plans, notes, route maps and context packs so a later session can pick up where the last
one stopped, and ship a PreCompact hook (requires Node.js) that saves ticket context before Claude compacts the conversation.
Install
Option A: Claude Code plugin
In Claude Code:
Plugin skills are namespaced, e.g. /workbench:jira-ticket-workbench. Update with
/plugin marketplace update workbench-skills.
Option B: Install script (global or project)
- **Global** installs to ~/.claude/skills/ — available in every project.
- **Project** installs to /.claude/skills/ — commit it to share with your team.
Script-installed skills are not namespaced, e.g. /jira-ticket-workbench.
**Windows (PowerShell)** — interactive:
With options:
**macOS / Linux / Git Bash:**
**From a clone:**
On Windows (the default execution policy blocks running .ps1 files directly):
| PowerShell | Bash | Meaning |
|---|---|---|
| -Scope global\|project | --scope global\|project | Where to install. Prompted if omitted (interactive only). |
| -Path | --path | Project root for project scope. Default: current directory. |
| -Ref | --ref | Branch or tag to download. Default: main. |
| -Uninstall | --uninstall | Remove this repo's skills from the target. |
Update and uninstall
Re-run the same install command to update — each skill folder is replaced with the latest
version. Add -Uninstall / --uninstall to remove them. Other skills in the target folder
are never touched.
Adding a skill
1. Create skills/ /SKILL.md with name and description frontmatter.
project, organized by ticket (Jira, Azure DevOps, ...).
Currently supports **Claude Code**. Codex and Antigravity support is planned.
Skills
| Skill | What it does |
|---|---|
| jira-ticket-workbench | Tracks Jira issues and their linked Confluence pages in jira-workbench/. Needs the Atlassian Rovo MCP connector. |
| ado-ticket-workbench | Tracks Azure DevOps work items in ticket-workbench/. Needs an Azure DevOps MCP server. |
Both skills keep per-ticket plans, notes, route maps and context packs so a later session can pick up where the last
one stopped, and ship a PreCompact hook (requires Node.js) that saves ticket context before Claude compacts the conversation.
Install
Option A: Claude Code plugin
In Claude Code:
Plugin skills are namespaced, e.g. /workbench:jira-ticket-workbench. Update with
/plugin marketplace update workbench-skills.
Option B: Install script (global or project)
- **Global** installs to ~/.claude/skills/ — available in every project.
- **Project** installs to /.claude/skills/ — commit it to share with your team.
Script-installed skills are not namespaced, e.g. /jira-ticket-workbench.
**Windows (PowerShell)** — interactive:
With options:
**macOS / Linux / Git Bash:**
**From a clone:**
On Windows (the default execution policy blocks running .ps1 files directly):
| PowerShell | Bash | Meaning |
|---|---|---|
| -Scope global\|project | --scope global\|project | Where to install. Prompted if omitted (interactive only). |
| -Path | --path | Project root for project scope. Default: current directory. |
| -Ref | --ref | Branch or tag to download. Default: main. |
| -Uninstall | --uninstall | Remove this repo's skills from the target. |
Update and uninstall
Re-run the same install command to update — each skill folder is replaced with the latest
version. Add -Uninstall / --uninstall to remove them. Other skills in the target folder
are never touched.
Adding a skill
1. Create skills/ /SKILL.md with name and description frontmatter.
- Source
- github · https://github.com/dngioidev/workbench-skills
- Browse by field
- Open source
- added
- 3d ago
More in Open source
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.