docs: add Microsoft Clarity setup skill

[harrisboatworks]

Summary

• document stable Clarity project and tracking-code routes
• capture the email-verification lock and ARIA option selector
• add consent-gated network verification checks for the tag and collect endpoint

Validation

• documentation only
• git diff --check passes
• excludes verification links, cookies, tokens, and user-specific state

---

Summary by cubic

Adds a Microsoft Clarity project setup domain skill with clear install checks, stable routes, and consent-aware network verification. Improves reliability by using ARIA roles and project IDs instead of fragile selectors.

• New Features
  • Documents stable routes for projects, onboarding, and tracking code.
  • Explains email verification lock and how to unblock project actions.
  • Adds consent-gated verification steps: tag URL, pre/post-consent checks, and expected 200/204 responses from clarity.ms.

^{Written for commit aff7946. Summary will update on new commits.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aff794602e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Move the Clarity skill to its discoverable directory

When BH_DOMAIN_SKILLS=1, the harness only auto-discovers skills from the directory that helpers.goto_url derives as hostname.removeprefix('www.').split('.')[0] (also covered by tests/unit/test_helpers.py), so https://clarity.microsoft.com maps to agent-workspace/domain-skills/clarity/, not this new clarity-microsoft-com/ directory. As a result, navigating to Clarity will not surface this skill to agents unless they manually search for it, defeating the purpose of adding the domain skill.

Useful? React with 👍 / 👎.

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="agent-workspace/domain-skills/clarity-microsoft-com/project-setup.md">

<violation number="1" location="agent-workspace/domain-skills/clarity-microsoft-com/project-setup.md:3">
P2: The directory is named `clarity-microsoft-com/` but when `BH_DOMAIN_SKILLS=1` is set, `goto_url` derives the skill directory from the navigated hostname. For `https://clarity.microsoft.com`, this likely resolves to `clarity/` (or possibly `clarity-microsoft-com/` depending on exact parsing), not matching this directory name. If the harness uses `hostname.removeprefix('www.').split('.')[0]` (as suggested by the helper tests), this skill won't be auto-surfaced to agents navigating Clarity. Consider renaming the directory to match the harness's actual host-to-directory mapping.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The directory is named clarity-microsoft-com/ but when BH_DOMAIN_SKILLS=1 is set, goto_url derives the skill directory from the navigated hostname. For https://clarity.microsoft.com, this likely resolves to clarity/ (or possibly clarity-microsoft-com/ depending on exact parsing), not matching this directory name. If the harness uses hostname.removeprefix('www.').split('.')[0] (as suggested by the helper tests), this skill won't be auto-surfaced to agents navigating Clarity. Consider renaming the directory to match the harness's actual host-to-directory mapping.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At agent-workspace/domain-skills/clarity-microsoft-com/project-setup.md, line 3:

<comment>The directory is named `clarity-microsoft-com/` but when `BH_DOMAIN_SKILLS=1` is set, `goto_url` derives the skill directory from the navigated hostname. For `https://clarity.microsoft.com`, this likely resolves to `clarity/` (or possibly `clarity-microsoft-com/` depending on exact parsing), not matching this directory name. If the harness uses `hostname.removeprefix('www.').split('.')[0]` (as suggested by the helper tests), this skill won't be auto-surfaced to agents navigating Clarity. Consider renaming the directory to match the harness's actual host-to-directory mapping.</comment>

<file context>
@@ -0,0 +1,81 @@
+# Microsoft Clarity — project setup and installation checks
+
+Host: `https://clarity.microsoft.com`
+
+## Useful routes
</file context>