Individual skill
seo-answer-visibility
Observe answer visibility for approved buyer questions, audit discoverability and file evidence-backed improvement cards.
employees/seo-employee/routines/seo-answer-visibility/SKILL.md
Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 878
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-employee Repository topic
- ai-employees Repository topic
- antigravity Repository topic
- automation Repository topic
- claude-code Repository topic
- claude-skill Repository topic
- codex Repository topic
- hermes-agent Repository topic
- openclaw Repository topic
- marketing Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
## Shared work cycle
After the guard returns `run`, read `WORK-CYCLE.md` and your entry in `work-profile.json`. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period `run` with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.
# Answer visibility
Run `node scripts/guard.mjs seo-answer-visibility --json` first. A non-run verdict has already been recorded; exit without reading the rest of the kit. For a run verdict read CONTRACT.md, ROLE.md, CAPABILITIES.md, AEO-PLAYBOOK.md and your SCHEDULE.md row in full. This routine inherits every contract guard, status, state schema, mutex rule and output writer boundary. Never infer a time, budget or cadence from this document.
## 0. Begin a recoverable run
Read your row and compute its period key using the contract rules and local clock. Read `state/seo-answer-visibility.json`. Apply the contract's once-per-period check and atomic state update, recording `last_period`, `started`, the run id and progress before external work. A real guard run returns an atomic claim. Preserve its token and apply WORK-CYCLE.md recovery rules; an inspection with --no-record reserves nothing. Use the established mutex/stale-lock rules before browser work, and release only the lock you own on every exit. Do not modify another routine's state, schedule or active lock.
Resolve capabilities live. Prefer a confirmed connected read route, then an approved browser session, then a dated member-supplied observation. CAPABILITIES.md is the only vendor-to-capability map. No connector purchase, install, account creation, authentication or credential entry. An unavailable route is an explicit gap, not zero visibility. Read-only observation includes submitting the approved public buyer question to an existing authorized search/chat surface; never include private client notes, secrets or unpublished strategy in that question. Do not use a route whose use requires accepting terms or an unapproved paid action.