feat(skills): react-only handling - #3466
Conversation
Soran and Juan Miguel expect an emoji acknowledgement from the captain, not a reply. The skill makes that explicit: two reactions, no text ever, and a four-minute hold on the eyes reaction so it reads as a person opening the message rather than an automated ack. Also records the picker's space-separated emoji names, which do not match the colon or hyphen forms and silently find nothing.
A skill nothing loads is dead weight, so the section 13 trigger and the audience classification land with it.
Confidence Score: 3/5This PR should not merge until the captain-specific policy is moved out of the shared template and the four-minute continuation uses a concrete supported scheduling mechanism. The shared runtime unconditionally embeds one captain's colleague-specific preferences, and the required delayed reaction cannot be scheduled through the documented wake queue as instructed. Files Needing Attention: .agents/skills/slack-react-only/SKILL.md and AGENTS.md Reviews (1): Last reviewed commit: "docs: declare the slack-react-only load ..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| Soran and Juan Miguel are the only two people this covers. |
There was a problem hiding this comment.
When another operator clones this shared template, the unconditional skill applies this captain's colleague-specific emoji-only policy to that operator's Slack contacts, causing legitimate messages from people with these names to be handled according to an unrelated personal preference. This conflicts with the requirement that shared surfaces remain generic and personal preferences stay private to the owning home.
Context Used: If there is a VISION.md file at the root of the re... (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| The colon form (`:thumbsupparrot:`) and the hyphen form match nothing in the picker. | ||
| The label is on the gridcell's child button, not on the gridcell itself. |
There was a problem hiding this comment.
When a qualifying request arrives before its four-minute hold has elapsed, this instruction delegates the continuation to a wake even though the documented wake queue only records immediate events at the current epoch. The required reaction therefore cannot be scheduled through that queue as instructed, causing it to be sent immediately or never delivered.
austingmhuang
changed the title
1 participant
asdf