Individual skill
weekly-loop
Product weekly loop on the focus page: judge the last change, propose one next change with evidence.
plugins/loomaly/loomaly/skills/weekly-loop/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,532
- 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
- engineering 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,011 bytes
Read excerpt
# Weekly loop on the focus page
1. `status` → `todo` → `focus`. If no brief, ask once and `set_goals`. If no focus page, suggest a candidate and `set_goals` with `page` after the owner picks.
2. Report the week in short: Search numbers from `focus` / `visibility` `view: google` (and rankings/ai when stored), and each change verdict. Say when traffic is too thin to judge. For paid refreshes use `check` with estimate → maxCost.
3. If any change is `watching`, recommend nothing new. Otherwise recommend **one** change: checkup `fail` items first, then the top open plan item from `todo` (it already carries the fix).
4. Wait for the owner's yes. When it ships, `set_goals` with `summary` / `shippedOn` / `ref`, then `check` with `target: fix` and the PR URL as `ref`.
5. Foundations in `todo` beat focus-page tweaks. Connect Google with `google` when needed.