القائمة
Walk through the tools in .quiddity/tools.json and help install any missing CLIs or MCPs. Run /q-which-tools first if tools.json doesn't exist.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Scan the current project and create a summary of its structure, important files, and conventions in .quiddity/project.md.
Generate a custom /next-task skill for your project. Ensures your issue tracker, source control, and CI are configured via /q-which-tools, then writes a tailored skill that picks up the next task, implements it, and opens a PR.
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.
Run the full Quiddity setup flow. Discovers your process and tools, then generates custom /new-issue, /next-task, and /approve skills for your project.
Discover what tools a project uses and save the configuration to .quiddity/tools.json. Pass category names as arguments (e.g., /q-which-tools issues source-control).
Generate a custom /approve skill for your project. Ensures your source control, CI, and PR conventions are configured via /q-which-tools, then writes a tailored skill that verifies checks and merges approved PRs.
| name | q-setup-tools |
| description | Walk through the tools in .quiddity/tools.json and help install any missing CLIs or MCPs. Run /q-which-tools first if tools.json doesn't exist. |
You are helping the user set up the CLIs and MCPs needed by their project's tools. Your job is to check what's already installed, guide setup for anything missing, and let the user skip anything they don't want.
.quiddity/tools.json must exist. If it doesn't, tell the user to run
/q-which-tools first and stop.
tool-registry.json (in the same directory as this skill) maps tool names to
recommended CLIs and MCPs. Load it at the start.
Read tools.json. Collect all unique tool values from every category.
Match against the registry. For each tool name found in tools.json, look
it up in tool-registry.json. Tools not in the registry are fine — just note
them as "no setup recommendations available" and move on.
Check what's already installed. For each matched tool:
verifyCommand from the registry. If it succeeds, the
CLI is already installed. If it fails or the command is not found, it needs
setup..claude/settings.json, .mcp.json, or ~/.claude.json for an existing
entry matching the package name.Present a summary. Show the user a table of all tools, what's installed
vs. what's missing. For tools with only a notes field in the registry,
display the note. For example:
Tool CLI MCP
GitHub gh (ok) —
GitHub Actions (no setup needed — runs in CI)
Linear — Linear MCP (not found)
Walk through missing items. For each tool with something missing:
installCommand from the registry. After
installation, run verifyCommand to confirm it worked. If the CLI needs
authentication (like gh auth login), walk the user through it.claude mcp add with the package name from the registry, or guide them
to add it manually. Link to the docsUrl for reference.Summarize. Show what was set up, what was skipped, and any manual steps the user still needs to take (e.g., authentication, API keys).