003-skills/.claude/skills/nixtla-plugin-scaffolder/SKILL.md
Generate production-ready plugin structures from PRD documents with enterprise-compliant files. Use when scaffolding new plugins, converting PRDs to plugin skeletons, or initializing plugin projects. Trigger with 'scaffold plugin', 'create plugin from PRD', or 'initialize plugin structure'.
npx skillsauth add intent-solutions-io/plugins-nixtla nixtla-plugin-scaffolderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Rapidly scaffold production-ready Claude Code plugin structures from PRD documents, generating all required files with enterprise compliance standards.
This skill transforms PRD documents into complete plugin scaffolds:
Required:
000-docs/000a-planned-plugins/*/02-PRD.md formatOptional:
jq: For JSON validation (install via apt install jq or brew install jq)Locate the PRD document for the plugin to scaffold:
ls 000-docs/000a-planned-plugins/*/02-PRD.md
Execute the scaffolding script with the PRD path:
python {baseDir}/scripts/scaffold_plugin.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-roi-calculator/02-PRD.md \
--output 005-plugins/nixtla-roi-calculator
The script creates a complete plugin structure:
005-plugins/nixtla-roi-calculator/
├── plugin.json # Plugin metadata and configuration
├── README.md # Plugin documentation
├── .claude/
│ ├── skills/
│ │ └── nixtla-roi-calculator/
│ │ └── SKILL.md # Main skill definition
│ ├── commands/ # Slash commands
│ └── agents/ # Custom agents
├── scripts/
│ └── roi_mcp_server.py # MCP server implementation
└── tests/
└── test_roi_calculator.py # Test suite
Edit the generated files to match specific requirements:
Run the plugin validator to ensure compliance:
python 004-scripts/validate_skills_v2.py --verbose
Error: PRD file not found
Solution: Verify PRD path, check 000-docs/000a-planned-plugins/ directory
Error: Output directory already exists
Solution: Use --force flag to overwrite or choose different output path
Error: Invalid PRD format
Solution: Ensure PRD has required sections (Overview, Functional Requirements, MCP Server Tools)
Error: Permission denied creating directory
Solution: Check write permissions on target directory
Error: Missing plugin name in PRD
Solution: PRD must specify plugin name in header (e.g., **Plugin:** nixtla-roi-calculator)
python {baseDir}/scripts/scaffold_plugin.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-roi-calculator/02-PRD.md \
--output 005-plugins/nixtla-roi-calculator \
--author "Jeremy Longshore <[email protected]>" \
--license MIT
Generated plugin.json:
{
"name": "nixtla-roi-calculator",
"version": "0.1.0",
"description": "Enterprise ROI calculator for TimeGPT vs. build-in-house analysis",
"author": { "name": "Jeremy Longshore", "email": "[email protected]" },
"license": "MIT",
"mcpServers": {
"nixtla-roi-calculator": {
"command": "python",
"args": ["scripts/nixtla_roi_calculator_mcp_server.py"]
}
}
}
for prd in 000-docs/000a-planned-plugins/*/02-PRD.md; do
plugin_name=$(basename $(dirname "$prd"))
python {baseDir}/scripts/scaffold_plugin.py \
--prd "$prd" \
--output "005-plugins/$plugin_name"
done
python {baseDir}/scripts/scaffold_plugin.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-forecast-explainer/02-PRD.md \
--output 005-plugins/nixtla-forecast-explainer \
--template {baseDir}/assets/templates/plugin_custom.json
000-docs/6767-e-OD-REF-enterprise-plugin-readme-standard.md004-scripts/validate_skills_v2.pyRelated Skills:
nixtla-prd-to-code: Transform PRD into implementation tasksnixtla-demo-generator: Generate Jupyter notebook demosnixtla-test-generator: Create comprehensive test suitesScripts:
{baseDir}/scripts/scaffold_plugin.py: Main scaffolding script{baseDir}/assets/templates/plugin.json: Plugin metadata template{baseDir}/assets/templates/skill_template.md: SKILL.md templatetesting
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
tools
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
tools
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
development
This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".