new-tool

Scaffold Hugo tool bundles with front matter and integration metadata.

Updated Dec 14, 2025
One-click install
npx skills add https://github.com/kquinsland/tools --skill new-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-tool
Source: https://github.com/kquinsland/tools/tree/main/.github/skills/new-tool
Command: npx skills add https://github.com/kquinsland/tools --skill new-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A reliable, repeatable process to create new tool scaffolds, metadata, and integration steps for a Hugo-based site, reducing manual setup and deployment errors.

Core Features & Use Cases

  • Scaffolds a Hugo tool bundle under content/tools/<language>/<slug> with front matter and resources.
  • Documents the integration steps to include in the site build, icons, and assets for a consistent experience.
  • Provides a repeatable workflow for testing, documentation, and deployment.

Quick Start

Create a new tool bundle under content/tools/<language>/<slug>, add index.md with front matter, include the tool file and any resources, and follow the Tool Design Guidelines.

Frequently Asked Questions about new-tool

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

FAQPage Schema
How do I scaffold a new Hugo tool bundle with front matter and resources?

To scaffold a new Hugo tool bundle, create a directory under content/tools/<language>/<slug>, add an index.md file with required front matter fields like name, description, date, and resources, then include the tool file and any optional assets or scripts.

What front matter fields are required for Hugo tool documentation?

Required front matter fields for Hugo tool documentation include name, description, date, and resources. These metadata fields ensure the tool integrates properly into the site build and maintains consistent documentation standards across all contributed tools.

Does the Hugo tool creation workflow support optional scripts and asset directories?

Yes, the Hugo tool creation workflow supports optional scripts, references, and assets directories. This allows developers to include executable components and supplementary files alongside the standard index.md documentation within the tool bundle scaffold.

Why use a standardized scaffold for adding new tools to a Hugo site?

A standardized scaffold for adding new tools to a Hugo site reduces manual setup errors and ensures repeatable workflows for testing, documentation, and deployment. It provides a consistent end-to-end implementation guide for both content contributors and developers.

Can content contributors without development experience use this Hugo tool integration workflow?

Yes, content contributors can use this Hugo tool integration workflow. The process provides a defined end-to-end implementation guide and standardized front matter fields, making tool creation and documentation accessible without extensive development knowledge.

What is the best way to integrate a new tool into a Hugo site build end-to-end?

The best way to integrate a new tool into a Hugo site build is to scaffold a complete tool bundle under content/tools/<language>/<slug>, populate the front matter, add resources, and follow the defined end-to-end implementation guide for deployment.