Guidance: automations skill does not prevent incompatible / silent-fail setups

[adriannoes]

Problem

The automations skill (pipefy-automations) does not give agents enough guardrails to avoid incompatible event×action setups, opaque conditions, or the false belief that field_updated can move cards without AI.

Evidence

From live product testing against main:

• Tool docstring points at the automations skill, but the session still required get_automation_actions / get_automation_events to learn triggerEvents and accepted parameters.
• Condition shape/operations required GraphQL introspection (Automations: condition shape and operations only discoverable via introspection #387).
• Eight field_updated + move_single_card rules were created successfully and never ran (Automations: create accepts event×action combos that never fire #385).
• Live card create + log polling substituted for missing non-AI simulation (Automations: no dry-run / structural check for non-AI actions #388).

Impact

Skill is the intended routing layer for agents; when it omits the compatibility matrix and hard product limits, agents happily create silent-fail automations.

Status on dev

PARTIAL — pipefy-automations covers discover events/actions, create/update/simulate, and move-transition preflight notes. Missing: static or catalog-driven event×action matrix, ConditionInput guidance, explicit “field_updated does not move cards without AI” rule.

Possible directions (non-binding)

• Strengthen skill content: compatibility matrix, condition format, field_updated limitation, when to use AI vs traditional
• Keep skill thin and point at improved tool preflight/docs once Automations: create accepts event×action combos that never fire #385/Automations: condition shape and operations only discoverable via introspection #387/Automations: no dry-run / structural check for non-AI actions #388 land
• Add “debug why automation did not fire” checklist (read condition, check triggerEvents, logs vs dormant)

Related: #385, #387, #388, #389

Solution and acceptance criteria are decided when this issue is picked up.