setup-skills

Generates project docs spec files for tool configuration through a guided interview.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill setup-skills-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-skills
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/setup-skills
Command: npx skills add https://github.com/danielsuguimoto/skills --skill setup-skills-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Other skills in the repository depend on spec files under <project-root>/docs to know which tools (issue trackers, git hosts, databases, MCP servers) a project uses. Without these files, those skills cannot locate the tools they need, and manually writing 13 spec files is tedious and error-prone. ## Core Features & Use Cases - Guided Interview: Walks the user through three batches of questions covering issue trackers, bug trackers, git hosts, databases, code navigation, browser automation, knowledge graphs, containers, memory, terminal tools, doc lookup, and MCP servers. - Spec File Generation: Creates the <project-root>/docs folder and generates all 13 spec files, writing stubs for tools marked as not configured. - MCP Server Discovery: Detects available MCP servers and offers them as options during the interview, then documents them in mcp-servers.md. - Use Case: After cloning the skills repository into a new project, run the setup to produce a complete docs/ folder so skills like implement, pr-create, and database can resolve their tool references. ## Quick Start Ask the agent to run setup skills to configure the project docs folder and generate all tool spec files.

Frequently Asked Questions about setup-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the docs spec files required by these agent skills?▼

Invoke the setup flow, which detects your project root via git, interviews you about your tools in three question batches, and generates all 13 spec files under the docs folder. Tools you do not use get stub files marked as not configured.

What spec files does the skills setup generate?▼

It generates 13 files covering issue trackers, bug trackers, MCP servers, git hosts, database tools, code navigation, browser automation, knowledge graphs, container CLIs, memory providers, terminal wrappers, terminal tools, and doc lookup.

Can I regenerate only missing spec files instead of all of them?▼

Yes. The pre-flight check lists which of the 13 spec files already exist and asks whether to regenerate all files or only the missing ones. If all exist, you can choose to reconfigure or abort.

Does the setup detect MCP servers automatically?▼

Yes, when native MCP server discovery is available it builds an inventory of detected servers and offers them as options during the interview. Detected servers can be documented in the mcp-servers.md spec file.

What happens if I do not use a tool category like a bug tracker?▼

Select the None option during the interview. The setup writes a stub spec file marked as not configured, and skills referencing that spec will use fallbacks or skip that functionality.