Description and discovery
Write descriptions so hosts and agents can decide when an app is relevant. Include audience, jobs-to-be-done, required setup, expected artifacts, and clear non-goals. Avoid generic descriptions such as "helps with productivity". Discovery metadata should be compact; detailed usage belongs in the Markdown body or support files.
Checklist
- Keep declarations machine-readable.
- Keep procedures in Agent Skills.
- Keep facts in Agent Knowledge.
- Keep execution in the host runtime.
- Attach app provenance to projected objects.