review_post
shallowpro.aicut/aicut · Verify this server
OPENS THE PUBLISH CARD RIGHT HERE, in this conversation, for a post `prepare_post` has already staged. The user watches the actual video, sees which account it is going to, edits the caption if they want, picks the visibility, sets the commercial disclosure themselves, ticks a box saying they want it posted, and confirms twice. NOTHING IS PUBLISHED BY THIS CALL, and nothing is published by the card either. CALL IT IMMEDIATELY AFTER `prepare_post` ON ANY CLIENT THAT RENDERS CARDS, and then STOP. Say one short line - that the post is on screen for them to check - and wait. Do not recite the caption, do not list the privacy options, do not ask 'public or friends-only?', and do not ask whether they want it posted: every one of those questions is a control on the card, and asking it in chat is what this tool exists to replace. WHAT COMES BACK TO YOU IS A MESSAGE FROM THE USER, and it is your signal. The card writes one turn saying they approve, naming the destination, the visibility, the disclosure they set, and a post id. That id is a FRESH post staged from their own choices - use it, not the one `prepare_post` gave you. Call `publish_post` with it and nothing else, then poll `get_post_status`. UNTIL THAT MESSAGE ARRIVES THERE IS NOTHING TO DO. Do not poll, do not call `publish_post`, do not prepare the post again, and do not ask whether they have finished. If they say they cannot see a card, this client did not render one: fall back to asking them in the message, exactly as `publish_post` describes, and do not call this tool again. IF THEY CHANGE THEIR MIND IN THE CARD, no message arrives and nothing is staged. That is a complete outcome; do not chase it. WHEN NOT: there is no card surface at all - a terminal, a script, a CI job - because a card nobody can see is a dead end. Ask in the message instead. COSTS NOTHING AND SENDS NOTHING. This call reads a post you already prepared; it stages nothing, claims no quota slot, and reaches no platform. OUTPUT: the prepared post, for the card. There is nothing in it for the conversation - do not paste it and do not summarise it.
1 trials · measured 27 days ago
review_post scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against pro.aicut/aicut, measured 11 Sept 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-09-11 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/5da0a1f2-ad86-48ec-b884-f37aacbc876c)