skills.rest
zts212653
zts212653COMMUNITY
Explore all skills by this author →
GitHub

owner-friendly-plugin-development

Designs Clowder AI plugins with honest lifecycle states, in-product authorization, and verified release closures.

2.9k|733|Updated Mar 12, 2026
Search Tags:#lifecycle management#dogfooding#release verification#authorization flow#Plugin Development#clowder ai#ownership map
One-click install
npx skills add https://github.com/zts212653/clowder-ai --skill owner-friendly-plugin-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: owner-friendly-plugin-development
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/owner-friendly-plugin-development
Command: npx skills add https://github.com/zts212653/clowder-ai --skill owner-friendly-plugin-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plugins that merely "install and run" often fail their operators: a single enabled flag hides crashes, authorization flows dump raw terminal commands on users, monorepo hoisting masks broken release packages, and CI-green plugins never prove they removed real user labor. This Skill turns a real user journey into an installable, authorizable, state-honest, recoverable Clowder AI plugin product boundary.

Core Features & Use Cases

  • Journey-First Scoping: Freeze the before/after of eliminated human labor, human-retained decisions, and non-goals before touching SDK capabilities.
  • Ownership & Authority Mapping: Define what the external source, plugin, Host, cat, and operator each own, using bounded metadata and opaque source refs instead of leaking content across boundaries.
  • Five-Truth Lifecycle Model: Separate artifact, config, auth, intent, and live states so crashes, dormancy, and auth expiry are honestly projected with concrete recovery actions.
  • In-Product Auth & Release Closure: Keep device authorization, regrant, and repair inside the plugin card, and prove the packed artifact runs in a fresh consumer without monorepo hoisting.
  • Use Case: When designing a Feishu meeting-intake plugin, use this Skill to define the journey contract, state model, and dogfood evidence so the operator never downloads transcripts or hunts for threads manually.

Quick Start

Ask the AI to design an owner-friendly Clowder AI plugin for your integration idea, defining the user journey, ownership map, lifecycle states, and release evidence plan.

Frequently Asked Questions about owner-friendly-plugin-development

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

FAQPage Schema
How do I design an owner-friendly Clowder AI plugin?▼

Start by freezing the before/after of eliminated human labor, then map ownership across source, plugin, Host, cat, and operator. Model lifecycle as five separate truths (artifact, config, auth, intent, live) and keep authorization and recovery inside the plugin card.

When should I use this Skill instead of plugin-creator?▼

Use this Skill when the plugin has a Host lifecycle, background runtime, external events, or persistent user state. Use plugin-creator only for scaffolding a Codex plugin bundle, and skip this Skill for pure skills, MCP servers, or one-off API scripts.

Why does my plugin show running after a crash or restart?▼

A single enabled flag conflates user intent with process health. Project crashes and post-restart dormancy immediately into the live state, and never infer runtime status from the desired state.

How do I verify a plugin release package actually works?▼

Test the packed tarball in a blank consumer without monorepo hoisting, global installs, or symlinks. Confirm catalog pin, manifest, entry file, and SRI point to the same immutable bytes, then run the entry and key subcommands from the unpacked artifact.

Should plugin authorization show terminal commands to users?▼

No. Device authorization must stay in the plugin card with vendor-pinned domains, server-side device secrets, allowlisted child environment variables, and only a verification URL, user code, or QR shown to the operator.

Is CI passing enough to claim a plugin is done?▼

No. Contract tests prove schemas and permissions, but only a real dogfood run across discovery, setup, auth, enable, live work, recovery, and upgrade proves the mechanical steps actually disappeared for the user.

Related Skills

Explore More Software Engineering Skills→
masorangemasorange
7

titan-capability-discovery

Inspect .titan directories, plugin packages, and Titan docs to identify reusable workflows.

Official
Advanced
vencialleevenciallee

evidence-driven-software-engineering

Coordinate software engineering via evidence-backed plans, tests, and readiness decisions.

Community
Advanced
Vel-LabsVel-Labs

contract-fixture-author

Automate contract schema, fixture, and test coverage maintenance.

Official
Intermediate
MnkyArtsMnkyArts
5

hytale-plugin-basics

Create Hytale server plugins with lifecycle hooks and manifest.json structure.

Community
Basic