happyskills

Automate HappySkills skill and kit publishing with validation and dependency resolution.

4|Updated Oct 12, 2021
One-click install
npx skills add https://github.com/nicolasdao/puffy-core --skill happyskills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: happyskills
Source: https://github.com/nicolasdao/puffy-core/tree/main/.agents/skills/happyskills
Command: npx skills add https://github.com/nicolasdao/puffy-core --skill happyskills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The HappySkills CLI helps you install, manage, and publish Claude Code-style skills across your workspace with a unified, frontmatter-driven workflow.

Core Features & Use Cases

  • Post-init enrichment and ecosystem metadata (skill.json, keywords, dependencies, CHANGELOG)
  • Skill authoring guidance and frontmatter validation for reliable auto-invocation
  • Full lifecycle: install, update, check, refresh, publish, convert, fork, and more
  • Multi-agent support, visibility controls, and workspace collaboration

Quick Start

Create, design, and publish HappySkills skills and kits across your workspace with guided authoring and validation.

Frequently Asked Questions about happyskills

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

FAQPage Schema
How do I manage and publish skills across a multi-agent workspace?

Multi-agent workspace skill management is automated by orchestrating authoring, validation, dependency resolution, and deployment. It unifies the publishing lifecycle with predictable JSON-output formats for reliable automation.

What's the best way to validate frontmatter for reliable CLI skill auto-invocation?

Frontmatter validation for CLI skill auto-invocation is handled through guided authoring and enrichment checks. It ensures ecosystem metadata like keywords and dependencies are correctly structured for reliable execution.

How does dependency resolution work when installing skills in a workspace?

Dependency resolution works by resolving required skill connections during the install and update lifecycle. It validates connections automatically to ensure workspace stability across multi-agent deployments.

Can I use this workflow to convert and fork existing skills for different workspaces?

Yes, the full lifecycle workflow supports converting and forking existing skills for different workspaces. It manages post-init enrichment and ecosystem metadata to maintain consistency across forked instances.

Do I need JSON-output formats for predictable automation of skill deployment?

JSON-output formats are supported for predictable automation of skill deployment and management tasks. They provide structured command references and exact outputs required for automated multi-agent orchestration.

Why does skill auto-invocation fail after updating workspace dependencies?

Skill auto-invocation failures after updates usually stem from invalid frontmatter or unresolved dependencies. Running the built-in validation and refresh commands checks metadata integrity and resolves missing connections.