Individual skill
seo-ops
Ops loop: weekly report, hand work to developers, track fix progress, and read charts from tool text (tables and sparklines).
plugins/loomaly/loomaly/skills/seo-ops/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 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)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,068 bytes
Read excerpt
# SEO ops in chat
1. `status` then `report` `kind: weekly` (and `roi` if they ask about impact). Share `report` `kind: public` when they want a link.
2. `todo` for this week's plan. The top open item already carries the fix. For each item: `send_to_dev` (or `problem` if you need more detail) → paste the task. Do not open GitHub Issues.
3. When a PR opens: `check` with `target: fix` and the PR URL as `ref`. Loomaly awaits deploy if needed and announces on the next `status`. `todo` `view: links` for link suggestions; `triage` `decide_link` for each.
4. Relay each tool's `say`. Use `chart.table` / `sparkline` when present. Human steps use `handoff` toward `/account/...` — never `/dashboard`.
5. Paid data: `set_goals` for trackKeywords / competitors / aiPrompts → `visibility` to read → `check` without `maxCost` for an estimate → `check` with `maxCost` to spend. Do not invent numbers.