feat(uipath-troubleshoot): add classic Click silent no-op playbook

[Stefan-Virgil]

What

Adds classic-activities/playbooks/click-silent-no-op.md — the classic counterpart to the modern NClick silent no-op playbook. Covers a classic input activity (Click / Type Into / Send Hotkey) that reports Successful but has no effect (no exception, job Successful, zero Error logs).

Causes: input method unsupported by the target tech (SimulateClick / SendWindowMessages on Java/SAP/legacy Win32), covering overlay, wrong/duplicate element, ClippingRegion/CursorPosition offset, lost focus.

Key classic-specific point: the classic Click has no Verify Execution feature, so the miss is silent by design — branch (F) prescribes adding explicit outcome detection (Element Exists/Get Text + If) as the closer.

Distinct from existing classic playbooks

• ui-element-interaction-failed.md — ElementOperationException (throws). This one: nothing throws.
• ui-element-not-found.md / ui-activity-timeout.md — target never located.
• ui-activity-configuration-error.md — both SimulateClick + SendWindowMessages set (config error). This one: a single valid flag on an unsupported target tech.

Wiring

• classic-activities/summary.md — new row.
• Top-level references/summary.md — added classic to the no-signature routing row ("Job Successful but the action had no effect").

Notes

• Self-contained; no cross-skill imports.
• Companion coder-eval test ships in a separate PR (test/troubleshoot-classic-click-noop-simulate) — merge this playbook PR first so the test grades against the real playbook in CI.

🤖 Generated with Claude Code

[github-actions]

Claude finished @Stefan-Virgil's task in 2m 14s —— View job

---

PR Review: Classic Click Silent No-Op Playbook

• Gather context and read review criteria
• Read full diff and changed files
• Verify links and cross-references
• Check existing playbooks for consistency
• Post review findings

---

Summary

Adds a new classic-activities playbook (click-silent-no-op.md) covering the case where a classic Click / Type Into / Send Hotkey reports success but its action never landed — no exception, no error, job Successful. Wires it into classic-activities/summary.md and adds classic to the no-signature routing row in the top-level references/summary.md.

Change-by-Change Review

1. skills/uipath-troubleshoot/references/activity-packages/classic-activities/playbooks/click-silent-no-op.md (new, +76 lines)

OK

Well-structured playbook that follows the established pattern of sibling classic playbooks (frontmatter with confidence, Context/Investigation/Resolution sections, decision tree with lettered branches). Key observations:

• Frontmatter is valid YAML with confidence: medium — matches convention used by other playbooks (e.g., ui-element-interaction-failed.md).
• All four relative links to sibling playbooks (ui-element-interaction-failed.md, ui-element-not-found.md, ui-activity-timeout.md, ui-activity-configuration-error.md) resolve correctly — all files exist.
• The differentiation from existing playbooks is clearly stated in the Context section (lines 11–14) and covers all four adjacent cases.
• The key classic-specific insight — no Verify Execution feature, so the miss is silent by design — is front-loaded (line 17) and reinforced in branch (F) (line 74).
• Investigation steps are prescriptive with exact CLI commands and --output json (line 44).
• Decision tree (lines 59–63) is exhaustive with clean fall-through, and the universal branch (F) "add outcome detection" is called out as required on top of any cause fix (line 65).
• Approval gate at line 76 correctly references SKILL.md §1.10 for workflow edits.
• No cross-skill dependencies, no secrets, no personal paths.

2. skills/uipath-troubleshoot/references/activity-packages/classic-activities/summary.md (+1 line)

OK

New row inserted at line 15, between "UI Element Interaction Failed" and "Browser Could Not Open or Attach". The row's description is self-contained and accurately reflects the playbook content. The relative link [click-silent-no-op.md](./playbooks/click-silent-no-op.md) resolves correctly. Confidence is Medium, consistent with sibling entries.

3. skills/uipath-troubleshoot/references/summary.md (+1/−1)

OK

Single-word addition: classic added to the domain list in the no-signature routing table (line 196). The existing ui-automation entry already covered the modern NClick case; this addition makes the routing table aware that the classic package also has a no-signature playbook. Clean, minimal change.

What's Missing

Nothing identified. This is a reference addition to an existing skill — no new skill folder, no CODEOWNERS change needed, no test tasks required for a playbook-only addition. The PR description notes a companion coder-eval test ships in a separate PR.

Area Ratings

Area	Status	Notes
Frontmatter	OK	Valid YAML, confidence: medium matches convention
E2E Tests	OK	Not required — this adds a reference playbook to an existing skill, not a new skill folder
Skill Body	N/A	SKILL.md not modified
References & Assets	OK	All relative links resolve; summary tables correctly wired; no duplication with sibling playbooks
Repo Hygiene	OK	CODEOWNERS already covers /skills/uipath-troubleshoot/; no secrets or personal paths; changes scoped to troubleshoot skill only

Issues for Manual Review

• Domain accuracy: The claim that SimulateClick / SendWindowMessages are unsupported for Java/SAP/legacy Win32 targets (line 29) is core to branch (A). Worth a domain-expert sanity check against current UiPath documentation.
• Placement in summary table: The new row sits between "UI Element Interaction Failed" and "Browser Could Not Open or Attach". This is logically grouped with the other UI interaction playbooks, which makes sense, but the table might benefit from keeping all UI-related entries together before the non-UI entries. Current placement looks intentional and reasonable.

Conclusion

Clean, well-structured addition. The playbook follows established conventions, all links resolve, the differentiation from sibling playbooks is explicit, and the decision tree is comprehensive. No issues found — approve.

---