enact/docs/guide

Document how to define and publish Enact tools using enact.md manifests.

Updated Dec 30, 2025

Search Tags:#documentation #guide #publishing #llm #tool-development

Ready to run

npx skills add https://github.com/while-basic/enact-template --skill enact-docs-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enact/docs/guide
Source: https://github.com/while-basic/enact-template/tree/main/examples/guide
Command: npx skills add https://github.com/while-basic/enact-template --skill enact-docs-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a concise, repeatable framework for documenting how to create, publish, and operate Enact tools using a standardized enact.md manifest.

Core Features & Use Cases

Documentation Template: Includes frontmatter and Markdown body to guide tool authors.
Learning & Onboarding: Serves as a reference for new contributors to Enact tool development and deployment.
Use Case: A developer uses this guide to draft a new Enact tool—defining its name, inputs, outputs, and publishing process.

Quick Start

Use the Enact LLM Guide to understand the tool creation workflow and the required fields in enact.md.

Frequently Asked Questions about enact/docs/guide

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

FAQPage Schema

How do I define and publish an Enact tool using the enact.md manifest?▼

To define and publish an Enact tool, create an enact.md manifest containing required frontmatter fields like name, description, build, command, inputSchema, outputSchema, and version, alongside a descriptive Markdown body.

What frontmatter fields are required in an enact.md manifest for tool publishing?▼

The required frontmatter fields for an enact.md manifest include name, description, from, build, command, inputSchema, outputSchema, env, timeout, version, and tags, which standardize tool definitions across languages.

What is the best way to standardize LLM tool definitions across different workflows?▼

Standardize LLM tool definitions by using a concise, repeatable framework like the enact.md manifest, which provides documentation templates and required schemas for consistent tool development and deployment.

Can I use the Enact documentation guide to onboard new contributors to tool development?▼

Yes, the Enact documentation guide serves as a reference for learning and onboarding new contributors, providing templates and best practices for creating, publishing, and operating Enact tools.

Do I need to specify inputSchema and outputSchema when creating an Enact tool?▼

Yes, specifying inputSchema and outputSchema is required when creating an Enact tool to ensure the tool's inputs and outputs are properly defined within the enact.md manifest.

Why does my Enact tool deployment require a descriptive Markdown body in the manifest?▼

A descriptive Markdown body is required in the manifest to document the tool's functionality, providing a standardized template that guides authors and ensures clear tool documentation for deployment.