specflow-use
SolidConnect Rosetta locally with Grid Dynamics SpecFlow MCP. Trigger only when the user mentions SpecFlow or SpecFlow workspaces and if SpecFlow MCP is already installed.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- griddynamics
- Repository
- griddynamics/rosetta
- Created
- 4 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
spec-forge
Professional specification system for Codex. Use when the user asks to create, improve, review, audit, analyze, or propagate product/software documentation, including ideas, PRDs, SRS documents, technical designs, architecture/RFC docs, feature specs, test cases, documentation audits, document landscape analysis, and full idea-to-spec chains. Supports complex multi-skill orchestration: idea -> decompose -> tech-design + feature specs -> review, with optional PRD, SRS, test-cases, audit, analyze, and propagate workflows.
openapi-to-mcp
Build and deploy an MCP server from an OpenAPI / Swagger spec using the mcp-use TypeScript SDK. Use this skill whenever the user wants to "turn this OpenAPI spec into an MCP server", "make this API usable from Claude/ChatGPT", "wrap this Swagger doc as MCP tools", "expose this REST API to an LLM", "generate MCP tools from a spec", or pastes/attaches an `openapi.yaml`, `openapi.json`, or `swagger.json` and asks for a Claude-compatible version. Trigger even if the user doesn't say "MCP" — if they describe an existing HTTP API (REST endpoints, an internal service, a third-party API they have a key for) and want an LLM to call it, this is the right skill. Covers spec ingestion (file path, URL, or pasted), operation-to-tool mapping, auth wiring (apiKey, bearer, basic, OAuth bearer), scaffolding with `create-mcp-use-app`, tool generation with proper zod schemas, live testing in the mcp-use inspector, and deploying to Manufact / mcp-use cloud.
speckit-coach
Helps with SpecKit / Spec-Driven Development problems. Use when the user is stuck on: a failing simplicity gate or gate-validator rejecting acceptance criteria, deciding which checklist domains apply (api, security, observability, data-integrity, resilience), writing testable acceptance criteria the gate accepts, decomposing a large feature into multiple specs, creating a multi-spec technical roadmap, understanding the consensus protocol or how phase gates work, the difference between specify plan and specify tasks, what each /speckit-<command> does, how the tdd-mandate preset changes the workflow, where grill-me or clarify fit in the SDD process, repairing an existing speckit-pro project, making template customizations upgrade-safe, or browsing, installing, configuring, or removing SpecKit community extensions, presets, hooks, or catalog entries (verify, doctor, review, archive, retrospective, jira, azure-devops, and the rest of the upstream catalog). Not for actually running autopilot ($speckit-autopilot),