Owned product · Credential-free Poppy mission procedures
Poppy Skills Pack
An installed SharetoBoard skill pack routing explicit local, cloud, or combined Poppy missions without owning credentials.
Ownership disclosure
SharetoBoard is an independent third-party product ecosystem. Poppy membership is separate and managed by Poppy. SharetoBoard is not affiliated with or endorsed by Poppy.
The project decision
Operators need reusable Poppy procedures without silently switching transports, duplicating credit use, or leaking credentials into prompts.
Who it is for: SharetoBoard operators using TentaClaw locally, ShriMCP in the cloud, or an explicitly approved combination.
What works
Verified or explicitly documented behavior.
- The operator chooses local or cloud transport before execution.
- Destination, credit impact, and history-writing approval are explicit.
- Automatic cloud failover after a local write is refused to avoid duplicate state and credit use.
- The preparer passes positive cases and five unsafe-input refusal cases.
Known limitations
What this project is not allowed to claim yet.
- The local, cloud, and combined live missions have not all passed.
- The pack does not own, request, or persist Poppy credentials.
- It does not silently change transports or retry state-changing operations.
- A public package and distribution authority have not been selected.
Current evidence
The public claim must stay inside this boundary.
- 01Installed skill name is run-poppy-missions.
- 02Structural validation, mission preparation, and credential/streaming/boolean/size refusal tests pass.
- 03An independent forward test preserved transport choice and refused duplicate-risk failover.
Current blockerLocal, cloud, and combined live missions plus the public packaging decision remain open.
Next gateRun the three acceptance missions with explicit approvals, then choose and verify the public distribution authority.
Follow the next gate