Q Setup New Issue
Generate a custom /new-issue skill for your project. Ensures your issue tracker is configured via /q-which-tools, then writes a tailored skill that converts plain-English descriptions into well-structured issues.
Install
$ agentstack add skill-jlong-quiddity-q-setup-new-issue ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jlong-quiddity-q-setup-new-issue) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Setup /new-issue
You are generating a custom /new-issue skill for the user's project.
Required categories
This skill needs the following tools.json categories: issues
Process
- Ensure tools are configured. Check if
.quiddity/tools.jsonexists and
contains the issues category. If not, run /q-which-tools issues to configure it.
- Read the configuration. Load all available Quiddity context:
.quiddity/project.md— project structure, tech stack, issue templates.quiddity/process.md— issue workflow and conventions.quiddity/tools.json— extract theissuescategory
- Ask skill-specific questions not covered by tools.json:
- Should the skill accept a description as an argument?
(e.g., /new-issue Add dark mode support)
- Do issues need acceptance criteria generated automatically?
- Any standard sections? (description, steps to reproduce, expected behavior)
- Any issue templates already in use?
- Auto-assign issues to the creator?
- For UI-related issues, should the skill generate ASCII wireframes to
illustrate the proposed change? (Great for making layout and component ideas concrete before implementation.)
- Generate the skill. Write a complete
/new-issueSKILL.md to the
project's skills directory. The generated skill should:
- Accept a plain-English description (via
$ARGUMENTSor interactive prompt) - Generate a structured issue with proper title, description, and acceptance
criteria based on the user's conventions
- Apply the right labels, priority, and milestone using the configured tracker
- Create the issue via MCP or CLI based on the tool in tools.json
- Return the issue identifier and URL
- Reference
.quiddity/tools.jsonfor all tool-specific configuration
- Show the generated skill to the user and ask for confirmation before
finalizing.
Generated skill template
The generated /new-issue skill should follow this general structure, adapted to the user's specific tools:
---
name: new-issue
description: Create a new issue from a plain-English description.
argument-hint: "[description]"
---
# /new-issue
[Instructions tailored to the user's issue tracker, labels, states, etc.]Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jlong
- Source: jlong/quiddity
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.