springboot-api-from-template

Create API specification repositories from an HMCTS template with GitHub team details.

3|4|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill springboot-api-from-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: springboot-api-from-template
Source: https://github.com/hmcts/agentic-plugins-marketplace/tree/main/plugins/agents/hmcts-apim-sdlc-orchestrator/skills/springboot-api-from-template
Command: npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill springboot-api-from-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the automated generation of new API specification repositories using a standardized template, reducing the effort and time spent on repository setup.

Core Features & Use Cases

  • Template-Based Creation: Automatically stands up new API spec repos using a predefined HMCTS template, ensuring consistency and speed.
  • Repo Naming Convention: Follows HMCTS Marketplace naming conventions to facilitate easy identification and organization.
  • User Input Collection: Collects necessary inputs such as repository name, owning GitHub team, short description, product team context, API version, and primary consumers to tailor the repository appropriately.

Quick Start

Execute the skill with the command: /use springboot-api-from-template

Frequently Asked Questions about springboot-api-from-template

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

FAQPage Schema
How do I create a new API specification repository using an HMCTS template?

To create an API specification repository, execute the skill to automatically stand up a new repo from a predefined HMCTS template, ensuring it adheres to coding standards and naming conventions. You must provide valid GitHub team information, a short description, and product team context.

What inputs are required to automate HMCTS API repository creation?

Automating HMCTS API repository creation requires you to supply the repository name, owning GitHub team, short description, product team context, API version, and primary consumers to tailor the repository appropriately.

Does the HMCTS API template enforce marketplace naming conventions?

Yes, the HMCTS API template enforces marketplace naming conventions to facilitate easy identification and organization of your newly created API specification repositories.

Can I use this template generation for non-HMCTS software engineering projects?

No, this template generation applies specifically to software engineering teams creating API specifications within HMCTS, ensuring repositories adhere to internal coding standards.

What is the best way to standardize new OpenAPI repositories for a product team?

The best way to standardize OpenAPI repositories is using an automated canonical template that collects product team context and applies consistent repository naming conventions during creation.

Why do I need to provide GitHub team information for API spec repository setup?

You need to provide GitHub team information during API spec repository setup to correctly assign ownership and tailor the repository to the specific product team context within HMCTS.