Should ACP examples cover plugin + Skill packaging and eval metadata?

[rforgeon]

Hi ACP maintainers - would a small examples/RFD contribution around plugin + Skill packaging fit this repo?

I checked the repo first and saw AGENTS.md, CLAUDE.md, the agent registry docs, MCP-over-ACP docs, and an agent telemetry export RFD. I did not see guidance for packaging an ACP-compatible agent capability as an installable plugin with Skills/evals.

The contribution I have in mind is protocol-adjacent rather than product-specific:

• an example note showing how an ACP agent or tool surface can be packaged as an installable plugin
• a distinction between the plugin package, individual Skills/capabilities, MCP/tool access, and eval metadata
• a privacy boundary for telemetry/export: no prompts, tool arguments, file contents, connector payloads, or model outputs
• optional Telvine-style distribution/eval metadata as one concrete implementation, without making Telvine part of ACP itself

Would this kind of examples/RFD contribution be useful, or should plugin packaging guidance live outside the ACP repo?