Individual skill
seo
Fix SEO problems Loomaly ranks first: status → todo (fix is on the top item) → change code on a branch → check target fix with the PR link. For solo and developers.
plugins/loomaly/loomaly/skills/seo/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,533
- 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,108 bytes
Read excerpt
# Fix SEO in this repository
1. `status` (optional `domain`). If `needsSite`, find the domain and `add_site`. Poll `status` until `scan.phase` is `done` or `failed`.
2. `todo` for `weeklyPlan`. The top open item already carries `fixPrompt`, evidence, url, and verify. If `needsBrief`, ask once and `set_goals`. Foundations (sitemap, robots, Search Console, homepage) before ordinary findings. Use `google` when setup is required.
3. Solo: apply `fixPrompt` here. Team ops: `send_to_dev` for paste-ready task text. Call `problem` only when you need more detail.
4. Open a PR, then immediately `check` with `target: fix`, `findingId`, and `ref` = PR URL. Loomaly waits up to 40 s; if not deployed yet it awaits deploy and re-checks on its own. The next `status` announces the result.
5. `triage` `ignore` only when the owner says it is not a problem. Never invent Search Console or paid ranking numbers.