Team Issue
CheckedThis skill summarizes team issues from messages, streamlining communication and boosting productivity by quickly surfacing key concerns.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add catlog22/claude-code-workflow --skill team-issue -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
catlog22
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned catlog22/claude-code-workflow at 07491b04ac.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 07491b04ac
- Scanned
- 24 files, 3,145 lines
- Copies in repo
- 2 — all of them scanned
About this skill
The team-issue skill enables AI agents to interact with team-based issue tracking systems, allowing them to create, update, and query tasks within a collaborative workflow. It bridges the gap between code execution and project management by translating natural language requests into specific issue tracker actions.
When to use it
- You need an agent to automatically log bugs found during automated testing runs directly to your team's backlog.
- An agent should summarize daily code changes and propose new feature requests or tasks for human review.
- You want the agent to search existing issues for context before generating a solution to a reported problem.
- Your workflow requires updating issue statuses (e.g., moving from "To Do" to "In Progress") after code is committed.
Key capabilities
- Create new issues with custom titles, descriptions, and priority levels based on user input.
- Search and retrieve existing issues using keywords, assignees, or status filters.
- Update issue metadata such as labels, comments, and status assignments dynamically.
- Integrate seamlessly with team workflows to maintain synchronization between code and tasks.
Example prompts
- "Create a high-priority bug report for the login page timeout error we just fixed."
- "Search for any open issues related to the database migration script and summarize them."
- "Update issue #402 to 'In Progress' and assign it to the backend team lead."
Tips & gotchas
Ensure your AI agent has proper API credentials or permissions configured for your specific issue tracking platform before attempting operations. Be explicit about issue statuses and labels in prompts, as these often determine how humans triage work downstream.