@olegkoval/agent-skills 1.30.0 → 1.32.0

package/packages/software-development/shared-knowledge-artifact/adapters/claude/skills/shared-knowledge-artifact/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: shared-knowledge-artifact
+description: Build a shared, self-persisting knowledge ledger as a Claude Artifact — a private page that stores its own data, renders itself from that data, and saves new versions of itself, so several agents can read the same lessons before starting work and append to them afterwards. Use when the user wants agents to learn from each other, asks for a shared knowledge base, lessons-learned log, gotcha ledger, or cross-agent memory page they can hand to other sessions.
+license: MIT
+allowed-tools: Bash, Read, Write, Edit, Grep, Glob, Skill, Artifact
+compatibility: Claude Code only — requires the Artifact tool and the artifact runtime capabilities (`capabilities: {artifact: {}}`).
+metadata:
+  author: Oleg Koval
+  package: shared-knowledge-artifact
+  tags:
+    - artifacts
+    - knowledge-base
+    - multi-agent
+    - memory
+    - lessons-learned
+    - documentation
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# shared-knowledge-artifact
+
+Publish one private Artifact page that acts as an append-only knowledge ledger which multiple agents (and the user) read before starting work and write to when reality corrects them. The page **is** the record: it stores its own data and publishes new versions of itself, so nothing depends on a server or on local files.
+
+## Trigger phrases
+
+- create a shared artifact my other agents can learn from
+- shared knowledge base / lessons-learned log / gotcha ledger for agents
+- cross-agent memory page
+- somewhere agents can record what they learned so they don't repeat it
+
+## Before writing any code
+
+1. Invoke the `artifact-capabilities` skill — mandatory before declaring `capabilities` or writing any `window.claude.*` code.
+2. Invoke the `artifact-design` skill — calibrates the design treatment.
+3. Read the user's actual rules (`CLAUDE.md`, any verification/preferences doc, agent memory) and **seed the ledger with 6-10 real lessons already recorded there**. No lorem, no invented examples — a ledger that opens with fake entries never gets used.
+
+## Persistence mechanism
+
+- Declare `capabilities: {artifact: {}}` at publish time.
+- Store the data as a JSON object inside `<script type="application/json" id="ledger-state">`. That block is the authoritative record; the visible page is **rendered from it** at load. Never serialize the live DOM to save.
+- To persist: snapshot `document.documentElement.outerHTML` **once at script start** (pristine source, before any rendering), then on save splice the new JSON into that snapshot's `#ledger-state` block, prepend `<!doctype html>`, and call `artifact.publish(doc)`.
+- Get the namespace with `const artifact = await claude.use("artifact")`; branch on `null` (this view cannot write) and render a read-only state instead of a broken control.
+- Handle publish errors by code: `conflict` means someone published first and every view reloads to the winner — no retry, tell the person to re-add; `not_granted` / `not_writer` means read-only.
+- Publish only after an explicit user action, never on load; batch rapid edits into one publish.
+- Escape `</script` when writing the JSON back, and escape every interpolated note field on render.
+
+## Note schema
+
+One fact per entry:
+
+```json
+{"id":"n9","kind":"lesson|trap|pref","scope":"shell|review|github|...",
+ "title":"the rule in one line",
+ "body":"the concrete behaviour, specific enough to act on",
+ "why":"the failure that made this a rule",
+ "author":"model or agent name","date":"YYYY-MM-DD"}
+```
+
+Kinds: **lesson** = a habit that holds; **trap** = something that silently produces a *wrong* answer; **pref** = how the user wants the work done.
+
+## UI the page must have
+
+- Header: name, one paragraph on what the ledger is for, and live counts (total, traps, lessons, preferences) in `tabular-nums`.
+- Note list, newest first: kind tag, scope tag, author, date, title, body, and a `Why:` line. Kind tags use semantic colour (trap = critical, pref = warning, lesson = accent), separate from the page accent.
+- Scope filter chips derived from the data, including an `all` chip, with `aria-pressed` state.
+- An "Add a note" form (kind, scope, author, title, body, why) that appends to the JSON and publishes, with an inline status line reporting published / conflict / read-only.
+- A "Protocol for agents" section **on the page itself**: read the page with the Artifact tool `action: "read"` before substantive work; parse the `#ledger-state` JSON, never scrape the DOM; **append, don't rewrite**; re-read before writing because another agent may have published since; one fact per note with the failure that caused it. Include the schema snippet.
+- Gatekeeping copy: only non-obvious, durable, cross-cutting lessons. If a repo's `CLAUDE.md` already says it, or a review bot already catches it, leave it out — a littered ledger is worse than a thin one.
+
+## Design constraints
+
+- Utilitarian but genuinely polished: this is a reference document, not a landing page. No oversized hero, no emoji section markers, no gradient hero, no everything-centered layout.
+- Avoid the AI-default looks: warm cream + serif + terracotta, near-black + acid green, Inter or Space Grotesk as the "safe" face.
+- Pair a display face, a body face, and a mono utility face from Google Fonts (the only permitted external host), each with a real fallback stack.
+- Theme-aware in all three states: full light palette as tokens on bare `:root`; redefined under `@media (prefers-color-scheme: dark)` guarded as `:root:not([data-theme="light"])`; redefined again under `:root[data-theme="dark"]`. Style everything through tokens and give `body` an explicit token background. No colour whose only definition sits inside a media or `[data-theme]` block.
+- Layout with flex/grid + `gap`, not per-element margins. Wide content in its own `overflow-x: auto` container. Visible focus states. Respect `prefers-reduced-motion`.
+- Title: a short, specific noun-phrase product name (2-4 words), no dash-explainer. Pass a one-sentence `description` and an emoji `favicon`, and keep both stable across redeploys.
+
+## Deliverable
+
+Write the HTML to a file, publish it with the Artifact tool, then report:
+
+- the URL;
+- that it stays private until shared from the page's share menu;
+- the exact instructions another agent needs — read via Artifact `action: "read"` with that URL, and write by appending to `notes` and republishing **with `url` set to that URL** (a publish *without* `url` forks a separate artifact instead of updating this one).
+
+## Notes
+
+- The full copy-paste prompt version of this workflow lives in `references/prompt.txt` — hand it to another agent or session verbatim.
+- Redeploy by republishing the same file path in the same conversation, or by passing `url` from any other conversation.

package/packages/software-development/shared-knowledge-artifact/adapters/claude/skills/shared-knowledge-artifact/references/prompt.txt

@@ -0,0 +1,78 @@
+BUILD A SHARED AGENT-KNOWLEDGE ARTIFACT
+
+Goal
+Publish a single private Claude Artifact page that acts as an append-only, self-persisting
+knowledge ledger which multiple agents (and I) read before starting work and write to when
+reality corrects us. The page IS the record: it stores its own data and saves new versions of
+itself, so nothing depends on a server or on my local files.
+
+Before writing any code
+1. Load the artifact-capabilities skill (you must, before declaring capabilities or writing any
+   window.claude.* code) and the artifact-design skill (calibrates the design treatment).
+2. Read my global rules (CLAUDE.md / VERIFICATION.md / memory) and seed the ledger with 6-10
+   REAL lessons already recorded there. No lorem, no invented examples.
+
+Required behaviour
+- Declare capabilities: {artifact: {}} so the page can publish new versions of itself.
+- Store the data as a JSON object inside a <script type="application/json" id="ledger-state">
+  block. That block is the authoritative record; the visible page is RENDERED from it at load.
+  Never serialize the live DOM to save.
+- To persist: snapshot document.documentElement.outerHTML once at script start (pristine source,
+  before any rendering), then on save splice the new JSON into the #ledger-state block of that
+  snapshot, prepend <!doctype html>, and call artifact.publish(doc).
+- Get the namespace with: const artifact = await claude.use("artifact"); branch on null (view
+  cannot write) and render a read-only state instead of a broken control.
+- Handle publish errors by code: "conflict" means someone published first and every view reloads
+  to the winner (no retry - tell the person to re-add); "not_granted"/"not_writer" means
+  read-only. Publish only after an explicit user action, never on page load, and batch rapid
+  edits into one publish.
+
+Note schema (one fact per entry)
+  {"id":"...", "kind":"lesson|trap|pref", "scope":"shell|review|github|...",
+   "title":"the rule in one line", "body":"the concrete behaviour, specific enough to act on",
+   "why":"the failure that made this a rule", "author":"model or agent name",
+   "date":"YYYY-MM-DD"}
+Kinds: lesson = a habit that holds; trap = something that silently produces a WRONG answer;
+pref = how I want the work done.
+
+UI the page must have
+- Header: title, one-paragraph statement of what the ledger is for, and live counts
+  (total notes, traps, lessons, preferences) in tabular-nums.
+- Note list, newest first, each note showing kind tag, scope tag, author, date, title, body,
+  and a "Why:" line. Kind tags carry semantic colour (trap = critical, pref = warning,
+  lesson = accent) separate from the page accent.
+- Scope filter chips derived from the data, including an "all" chip, with aria-pressed state.
+- An "Add a note" form (kind select, scope, author, title, body, why) that appends to the JSON
+  and publishes, with an inline status line reporting published / conflict / read-only.
+- A "Protocol for agents" section, on the page itself, stating: read the page with the Artifact
+  tool action "read" before substantive work; parse the #ledger-state JSON, never scrape the DOM;
+  APPEND, don't rewrite; re-read before writing because another agent may have published since;
+  and one fact per note with the failure that caused it. Include a copyable JSON snippet of the
+  schema.
+- Gatekeeping copy: only non-obvious, durable, cross-cutting lessons. If a repo's CLAUDE.md
+  already says it or a review bot already catches it, leave it out. A littered ledger is worse
+  than a thin one.
+
+Design constraints
+- Utilitarian but genuinely polished; this is a reference document, not a landing page. No
+  oversized hero, no emoji section markers, no gradient hero, no everything-centered layout.
+- Avoid the AI-default looks: warm cream + serif + terracotta, near-black + acid green, Inter or
+  Space Grotesk as the safe face.
+- Pair a display face with a body face and a mono utility face from Google Fonts (the only
+  permitted external host), each with a real fallback stack.
+- Theme-aware in all three states: full light palette as tokens on bare :root, redefined under
+  @media (prefers-color-scheme: dark) guarded as :root:not([data-theme="light"]), and again under
+  :root[data-theme="dark"]. Style everything through tokens; body must set an explicit token
+  background. No colour whose only definition sits inside a media or [data-theme] block.
+- Layout with flex/grid + gap, not per-element margins. Wide content in its own overflow-x:auto
+  container. Visible focus states. Respect prefers-reduced-motion.
+- Escape all interpolated note text on render, and escape "</script" when writing the JSON back.
+- Title: a short, specific noun-phrase product name (2-4 words), no dash-explainer. Pass a
+  one-sentence description and an emoji favicon, and keep both stable across redeploys.
+
+Deliverable
+Write the HTML to a file, publish it with the Artifact tool, and report back: the URL, the fact
+that it is private until shared from the page's share menu, and the exact instructions another
+agent needs - read via Artifact action "read" with that URL, and write by appending to notes and
+republishing with `url` set to that URL (a publish WITHOUT url forks a separate artifact instead
+of updating this one).

package/packages/software-development/shared-knowledge-artifact/references/prompt.txt

@@ -0,0 +1,78 @@
+BUILD A SHARED AGENT-KNOWLEDGE ARTIFACT
+
+Goal
+Publish a single private Claude Artifact page that acts as an append-only, self-persisting
+knowledge ledger which multiple agents (and I) read before starting work and write to when
+reality corrects us. The page IS the record: it stores its own data and saves new versions of
+itself, so nothing depends on a server or on my local files.
+
+Before writing any code
+1. Load the artifact-capabilities skill (you must, before declaring capabilities or writing any
+   window.claude.* code) and the artifact-design skill (calibrates the design treatment).
+2. Read my global rules (CLAUDE.md / VERIFICATION.md / memory) and seed the ledger with 6-10
+   REAL lessons already recorded there. No lorem, no invented examples.
+
+Required behaviour
+- Declare capabilities: {artifact: {}} so the page can publish new versions of itself.
+- Store the data as a JSON object inside a <script type="application/json" id="ledger-state">
+  block. That block is the authoritative record; the visible page is RENDERED from it at load.
+  Never serialize the live DOM to save.
+- To persist: snapshot document.documentElement.outerHTML once at script start (pristine source,
+  before any rendering), then on save splice the new JSON into the #ledger-state block of that
+  snapshot, prepend <!doctype html>, and call artifact.publish(doc).
+- Get the namespace with: const artifact = await claude.use("artifact"); branch on null (view
+  cannot write) and render a read-only state instead of a broken control.
+- Handle publish errors by code: "conflict" means someone published first and every view reloads
+  to the winner (no retry - tell the person to re-add); "not_granted"/"not_writer" means
+  read-only. Publish only after an explicit user action, never on page load, and batch rapid
+  edits into one publish.
+
+Note schema (one fact per entry)
+  {"id":"...", "kind":"lesson|trap|pref", "scope":"shell|review|github|...",
+   "title":"the rule in one line", "body":"the concrete behaviour, specific enough to act on",
+   "why":"the failure that made this a rule", "author":"model or agent name",
+   "date":"YYYY-MM-DD"}
+Kinds: lesson = a habit that holds; trap = something that silently produces a WRONG answer;
+pref = how I want the work done.
+
+UI the page must have
+- Header: title, one-paragraph statement of what the ledger is for, and live counts
+  (total notes, traps, lessons, preferences) in tabular-nums.
+- Note list, newest first, each note showing kind tag, scope tag, author, date, title, body,
+  and a "Why:" line. Kind tags carry semantic colour (trap = critical, pref = warning,
+  lesson = accent) separate from the page accent.
+- Scope filter chips derived from the data, including an "all" chip, with aria-pressed state.
+- An "Add a note" form (kind select, scope, author, title, body, why) that appends to the JSON
+  and publishes, with an inline status line reporting published / conflict / read-only.
+- A "Protocol for agents" section, on the page itself, stating: read the page with the Artifact
+  tool action "read" before substantive work; parse the #ledger-state JSON, never scrape the DOM;
+  APPEND, don't rewrite; re-read before writing because another agent may have published since;
+  and one fact per note with the failure that caused it. Include a copyable JSON snippet of the
+  schema.
+- Gatekeeping copy: only non-obvious, durable, cross-cutting lessons. If a repo's CLAUDE.md
+  already says it or a review bot already catches it, leave it out. A littered ledger is worse
+  than a thin one.
+
+Design constraints
+- Utilitarian but genuinely polished; this is a reference document, not a landing page. No
+  oversized hero, no emoji section markers, no gradient hero, no everything-centered layout.
+- Avoid the AI-default looks: warm cream + serif + terracotta, near-black + acid green, Inter or
+  Space Grotesk as the safe face.
+- Pair a display face with a body face and a mono utility face from Google Fonts (the only
+  permitted external host), each with a real fallback stack.
+- Theme-aware in all three states: full light palette as tokens on bare :root, redefined under
+  @media (prefers-color-scheme: dark) guarded as :root:not([data-theme="light"]), and again under
+  :root[data-theme="dark"]. Style everything through tokens; body must set an explicit token
+  background. No colour whose only definition sits inside a media or [data-theme] block.
+- Layout with flex/grid + gap, not per-element margins. Wide content in its own overflow-x:auto
+  container. Visible focus states. Respect prefers-reduced-motion.
+- Escape all interpolated note text on render, and escape "</script" when writing the JSON back.
+- Title: a short, specific noun-phrase product name (2-4 words), no dash-explainer. Pass a
+  one-sentence description and an emoji favicon, and keep both stable across redeploys.
+
+Deliverable
+Write the HTML to a file, publish it with the Artifact tool, and report back: the URL, the fact
+that it is private until shared from the page's share menu, and the exact instructions another
+agent needs - read via Artifact action "read" with that URL, and write by appending to notes and
+republishing with `url` set to that URL (a publish WITHOUT url forks a separate artifact instead
+of updating this one).

package/packages/software-development/wikipedia-uk-editor/SKILL.md

@@ -34,7 +34,7 @@ Turn a URL or article title into a complete, policy-compliant Ukrainian Wikipedi
 A single deliverable written to a scratch file and echoed in chat:
 
 - the **target page** (exact ukwiki title, and whether it exists)
-- the **wikitext** — full article, or an exact-replacement section, or a precise before/after diff for small fixes
+- the **wikitext** — always the complete final article in one `.wiki` file, ready to paste over the whole edit box; never a diff, never a БУЛО/СТАЛО list of manual replacements
 - the **edit summary** in Ukrainian (≤ 200 chars)
 - the **source list** with the URL, publisher, and date actually fetched for each
 - **risk notes**: notability (ВП:ЗН) standing, anything a patroller will challenge, what still needs a human check
@@ -45,12 +45,15 @@ A single deliverable written to a scratch file and echoed in chat:
 
 | Input | Mode |
 |---|---|
+| explicit newcomer task (tier + type, e.g. "Середні → Оновлювати статті") | mode set by task type — see below |
 | en.wikipedia.org URL, no uk equivalent | **Translate** — new uk article |
 | uk.wikipedia.org URL, stub or thin | **Expand** |
 | uk.wikipedia.org URL with `{{Без джерел}}` / `{{Джерело}}` | **Source** |
 | uk.wikipedia.org URL, prose/format problems | **Cleanup** |
 | "what should I edit next" | **Plan** — read `references/strategy.md`, propose a ranked list |
 
+When a newcomer task type is given, it **overrides** the state-based guess above. The per-type scope contract in `references/newcomer-tasks.md` is binding — an assigned type is a ceiling on what the edit may touch, not a floor.
+
 Resolve the title first — `scripts/wiki.sh` handles redirects. Never draft against the wrong title.
 
 ### 2. Read before writing
@@ -60,6 +63,7 @@ Resolve the title first — `scripts/wiki.sh` handles redirects. Never draft aga
 ./scripts/wiki.sh get en "Title"          # source-language wikitext
 ./scripts/wiki.sh langlink en "Title" uk  # does a uk version already exist?
 ./scripts/wiki.sh check uk "Шаблон:Особа" # does this template/page exist?
+./scripts/wiki.sh tasks <type> [n]        # list candidates for a newcomer task type: copyedit|links|references|update|expand
 ```
 
 Stop and report if:
@@ -94,21 +98,38 @@ Run every item. Report failures rather than hiding them.
 - [ ] No original synthesis (ВП:ОД)
 - [ ] Dates, numbers, and name transliterations are Ukrainian-correct
 - [ ] Edit summary written in Ukrainian and states what changed and why
+- [ ] The edit stayed inside the assigned task type's allowed scope
+- [ ] Any maintenance template removed was actually earned — the underlying problem is genuinely fixed
 
 ### 6. Deliver
 
-Write the draft to a scratch file (`.md` alongside the raw `.wiki` text so paste is clean), print the edit summary, and tell the human exactly where to paste it:
+For Expand / Source / Cleanup: fetch the current wikitext, apply the changes programmatically (a small Python pass over the fetched file, asserting each anchor string matched exactly once), and write the whole resulting article out. Verify it before delivering — section list intact, every intended change landed, nothing else dropped.
+
+Write the draft to a scratch file: the raw `.wiki` file contains nothing but article wikitext (the full final article, ready to paste over the whole edit box); the human-readable explanation of what changed goes in a separate `.md`. Print the edit summary, and tell the human exactly where to paste it:
 
 - new article → `https://uk.wikipedia.org/wiki/Тайтл?action=edit`
-- section replace → name the section and its exact current heading
+- existing article → `https://uk.wikipedia.org/w/index.php?title=Тайтл&action=edit`, replace the whole edit box
 - test first → `Вікіпедія:Пісочниця` or the user's own `Користувач:Ім'я/Чернетка`
 
+End the delivery with a copy-to-clipboard command in its own fenced block, using a quoted absolute path — quoted because scratchpad paths contain characters the shell will otherwise mangle — always the raw `.wiki` file, never the `.md`:
+
+```sh
+pbcopy < "/absolute/path/to/slug.wiki"
+```
+
+Add an optional second line when the edit summary is long enough to be worth copying:
+
+```sh
+printf '%s' 'Опис редагування…' | pbcopy
+```
+
 Then stop. Do not offer to save it.
 
 ## References
 
 - `references/strategy.md` — the contribution strategy: what to farm, in what order, and how to build standing without getting flagged
 - `references/wikitext-uk.md` — verified uk templates, citation formats, article skeletons, policy shortcuts
+- `references/newcomer-tasks.md` — the newcomer task tiers (Легкі/Середні/Важкі) and the binding scope contract for each task type
 - `scripts/wiki.sh` — read-only MediaWiki API helper
 
 ## Verification

package/packages/software-development/wikipedia-uk-editor/adapters/claude/skills/wikipedia-uk-editor/SKILL.md

@@ -35,7 +35,7 @@ Turn a URL or article title into a complete, policy-compliant Ukrainian Wikipedi
 A single deliverable written to a scratch file and echoed in chat:
 
 - the **target page** (exact ukwiki title, and whether it exists)
-- the **wikitext** — full article, or an exact-replacement section, or a precise before/after diff for small fixes
+- the **wikitext** — always the complete final article in one `.wiki` file, ready to paste over the whole edit box; never a diff, never a БУЛО/СТАЛО list of manual replacements
 - the **edit summary** in Ukrainian (≤ 200 chars)
 - the **source list** with the URL, publisher, and date actually fetched for each
 - **risk notes**: notability (ВП:ЗН) standing, anything a patroller will challenge, what still needs a human check
@@ -46,12 +46,15 @@ A single deliverable written to a scratch file and echoed in chat:
 
 | Input | Mode |
 |---|---|
+| explicit newcomer task (tier + type, e.g. "Середні → Оновлювати статті") | mode set by task type — see below |
 | en.wikipedia.org URL, no uk equivalent | **Translate** — new uk article |
 | uk.wikipedia.org URL, stub or thin | **Expand** |
 | uk.wikipedia.org URL with `{{Без джерел}}` / `{{Джерело}}` | **Source** |
 | uk.wikipedia.org URL, prose/format problems | **Cleanup** |
 | "what should I edit next" | **Plan** — read `references/strategy.md`, propose a ranked list |
 
+When a newcomer task type is given, it **overrides** the state-based guess above. The per-type scope contract in `references/newcomer-tasks.md` is binding — an assigned type is a ceiling on what the edit may touch, not a floor.
+
 Resolve the title first — `scripts/wiki.sh` handles redirects. Never draft against the wrong title.
 
 ### 2. Read before writing
@@ -61,6 +64,7 @@ Resolve the title first — `scripts/wiki.sh` handles redirects. Never draft aga
 ./scripts/wiki.sh get en "Title"          # source-language wikitext
 ./scripts/wiki.sh langlink en "Title" uk  # does a uk version already exist?
 ./scripts/wiki.sh check uk "Шаблон:Особа" # does this template/page exist?
+./scripts/wiki.sh tasks <type> [n]        # list candidates for a newcomer task type: copyedit|links|references|update|expand
 ```
 
 Stop and report if:
@@ -95,21 +99,38 @@ Run every item. Report failures rather than hiding them.
 - [ ] No original synthesis (ВП:ОД)
 - [ ] Dates, numbers, and name transliterations are Ukrainian-correct
 - [ ] Edit summary written in Ukrainian and states what changed and why
+- [ ] The edit stayed inside the assigned task type's allowed scope
+- [ ] Any maintenance template removed was actually earned — the underlying problem is genuinely fixed
 
 ### 6. Deliver
 
-Write the draft to a scratch file (`.md` alongside the raw `.wiki` text so paste is clean), print the edit summary, and tell the human exactly where to paste it:
+For Expand / Source / Cleanup: fetch the current wikitext, apply the changes programmatically (a small Python pass over the fetched file, asserting each anchor string matched exactly once), and write the whole resulting article out. Verify it before delivering — section list intact, every intended change landed, nothing else dropped.
+
+Write the draft to a scratch file: the raw `.wiki` file contains nothing but article wikitext (the full final article, ready to paste over the whole edit box); the human-readable explanation of what changed goes in a separate `.md`. Print the edit summary, and tell the human exactly where to paste it:
 
 - new article → `https://uk.wikipedia.org/wiki/Тайтл?action=edit`
-- section replace → name the section and its exact current heading
+- existing article → `https://uk.wikipedia.org/w/index.php?title=Тайтл&action=edit`, replace the whole edit box
 - test first → `Вікіпедія:Пісочниця` or the user's own `Користувач:Ім'я/Чернетка`
 
+End the delivery with a copy-to-clipboard command in its own fenced block, using a quoted absolute path — quoted because scratchpad paths contain characters the shell will otherwise mangle — always the raw `.wiki` file, never the `.md`:
+
+```sh
+pbcopy < "/absolute/path/to/slug.wiki"
+```
+
+Add an optional second line when the edit summary is long enough to be worth copying:
+
+```sh
+printf '%s' 'Опис редагування…' | pbcopy
+```
+
 Then stop. Do not offer to save it.
 
 ## References
 
 - `references/strategy.md` — the contribution strategy: what to farm, in what order, and how to build standing without getting flagged
 - `references/wikitext-uk.md` — verified uk templates, citation formats, article skeletons, policy shortcuts
+- `references/newcomer-tasks.md` — the newcomer task tiers (Легкі/Середні/Важкі) and the binding scope contract for each task type
 - `scripts/wiki.sh` — read-only MediaWiki API helper
 
 ## Verification

package/packages/software-development/wikipedia-uk-editor/adapters/claude/skills/wikipedia-uk-editor/references/newcomer-tasks.md

@@ -0,0 +1,80 @@
+# Ukrainian Wikipedia newcomer task types
+
+Verified against the live `uk.wikipedia.org` API, 2026-08-20.
+
+`MediaWiki:NewcomerTasks.json` is the authoritative GrowthExperiments "Suggested edits"
+(Пропоновані редагування) task-type → maintenance-template map on ukwiki. The table below is
+that map.
+
+## Task-type mapping
+
+| ukwiki UI label | Tier | task type | Backing template(s) |
+|---|---|---|---|
+| Вичитувати | Легкі / easy | `copyedit` | `Шаблон:Мовні помилки` |
+| (not offered in UI — structured) | easy | `link-recommendation` | none |
+| (not offered in that UI list) | easy | `links` | `Шаблон:Упорядкувати`, `Шаблон:Брак посилань` |
+| Шукати зовнішні посилання | Середні / medium | `references` | `Шаблон:Без джерел` |
+| Оновлювати статті | Середні / medium | `update` | `Шаблон:Оновити` |
+| (not offered — structured) | medium | `image-recommendation`, `section-image-recommendation` | none |
+| Розширювати короткі статті | Важкі / hard | `expand` | `Шаблон:Доробити` |
+
+All six templates confirmed EXISTS. `Шаблон:Доробити` is a REDIRECT to `Шаблон:Заготовка`
+(see `references/wikitext-uk.md`).
+
+## Scope contract per task type
+
+An assigned task type is a **ceiling**, not a suggestion — overreach on a young account is what
+draws patrollers (see `references/strategy.md` Phase 1). Stay inside the type you picked.
+
+### `copyedit` — Вичитувати
+
+- IS: language, grammar, punctuation, typography fixes only.
+- NOT: no new facts, no new refs, no restructuring, no adding/removing/reordering sections.
+- Remove `{{Мовні помилки}}` in the same edit only if the whole article was actually proofread.
+- Edit summary shape: `Вичитка: виправлено [конкретні помилки]`.
+
+### `links` — Упорядкувати / Брак посилань
+
+- IS: wikilinks and formatting only.
+- NOT: no prose rewriting.
+- Edit summary shape: `Впорядкування посилань: [що додано/виправлено]`.
+
+### `references` — Шукати зовнішні посилання
+
+- IS: add inline `<ref>` to claims that are **already there**.
+- NOT: never rewrite a claim to fit a source you happened to find. If no source supports it as
+  written, report it — do not reshape it.
+- Remove `{{Без джерел}}` only when every substantive claim is cited.
+- Edit summary shape: `Додано джерела: [що саме підтверджено]`.
+
+### `update` — Оновлювати статті
+
+- IS: replace outdated values/dates/status with sourced current ones, plus the minimum prose the
+  change forces.
+- NOT: no scope expansion, no new sections.
+- Every updated number needs a source actually fetched this session — this is the highest
+  fabrication-risk type in the set and SKILL.md Hard Rule 2 applies with no exceptions.
+- Edit summary shape: `Оновлено дані: [що змінено] за станом на [дата]`.
+
+### `expand` — Розширювати короткі статті
+
+- IS: the **only** type permitted to add sections and substantial new sourced prose. Routes into
+  the existing **Expand** mode in SKILL.md.
+- `{{Заготовка}}` comes off only when the article genuinely stops being a stub.
+- Edit summary shape: `Розширено статтю: додано [розділи/теми], джерела`.
+
+## Out of scope: structured task types
+
+`link-recommendation`, `image-recommendation`, and `section-image-recommendation` are served
+through the Growth UI's own accept/reject widget on ukwiki, not by pasting wikitext. This skill
+does not improvise a manual equivalent for them — say so plainly and decline rather than draft
+around it.
+
+## Finding candidates
+
+`action=query&list=growthtasks` requires login, so this read-only skill cannot use it. Find
+candidate articles for a task type instead with:
+
+```sh
+./scripts/wiki.sh tasks <type> [n]
+```

package/packages/software-development/wikipedia-uk-editor/adapters/claude/skills/wikipedia-uk-editor/references/strategy.md

@@ -31,6 +31,16 @@ Rules for this phase: one change per edit, always an edit summary in Ukrainian,
 
 Target: ~30–50 edits, **zero reverts**. A revert in this phase costs more than 50 edits gain.
 
+### Newcomer tasks as a ready-made Phase 1 queue
+
+Ukrainian Wikipedia's own GrowthExperiments "Suggested edits" (Пропоновані редагування) tiers a
+maintenance backlog into Легкі / Середні / Важкі — see `references/newcomer-tasks.md` for the
+full mapping and per-type scope contract. Легкі (`copyedit`) and Середні (`references`, `update`)
+are lower-risk, community-endorsed work for this phase, but they are not zero-revert-risk:
+sourcing and fabrication risks still require verification. Pick candidates
+with `./scripts/wiki.sh tasks <type>` and stay strictly inside the assigned scope. Важкі
+(`expand`) is not Phase 1 work — it belongs in Phase 2 stream A/B, once autoconfirmed.
+
 ## Phase 2 — the volume engine (weeks 2–8)
 
 Four streams, run in parallel, roughly in this priority order. Value per unit of effort, highest first:

package/packages/software-development/wikipedia-uk-editor/adapters/claude/skills/wikipedia-uk-editor/scripts/wiki.sh

@@ -10,6 +10,7 @@
 #   wiki.sh search   <lang> <query> [n]      search article titles
 #   wiki.sh backlog  <category> [n]          list pages in a uk category (maintenance backlogs)
 #   wiki.sh info     <lang> <title>          length, last edit, categories, templates used
+#   wiki.sh tasks    <type> [n]              candidate articles for a newcomer task type
 set -eu
 
 UA="wikipedia-uk-editor-skill/1.0 (https://github.com/oleg-koval/agent-skills)"
@@ -24,7 +25,7 @@ api() {
 jqp() { python3 -c "$1"; }
 
 cmd=${1:-}
-[ -n "$cmd" ] || { sed -n '2,14p' "$0"; exit 1; }
+[ -n "$cmd" ] || { sed -n '2,13p' "$0"; exit 1; }
 shift
 
 case "$cmd" in
@@ -92,7 +93,62 @@ print('touched:',p.get('touched'))
 print('cats   :', ', '.join(c['title'] for c in p.get('categories',[])) or '(none)')
 print('tmpls  :', ', '.join(t['title'] for t in p.get('templates',[])) or '(none)')"
     ;;
+  tasks)
+    type=${1:-}
+    n=${2:-20}
+    case "$n" in
+      ''|*[!0-9]*) echo "Invalid task limit: '$n' (expected a non-negative integer)" >&2; exit 1 ;;
+    esac
+    case "$type" in
+      copyedit)   templates="Шаблон:Мовні помилки" ;;
+      links)      templates="Шаблон:Упорядкувати|Шаблон:Брак посилань" ;;
+      references) templates="Шаблон:Без джерел" ;;
+      update)     templates="Шаблон:Оновити" ;;
+      expand)     templates="Шаблон:Доробити" ;;
+      *)
+        echo "Unknown task type: '$type'. Valid types: copyedit, links, references, update, expand" >&2
+        exit 1
+        ;;
+    esac
+    [ "$n" -gt 0 ] || exit 0
+    results=$(mktemp)
+    trap 'rm -f "$results"' EXIT
+    oldifs=$IFS
+    IFS='|'
+    for tmpl in $templates; do
+      IFS=$oldifs
+      api uk --data-urlencode "action=query" --data-urlencode "list=embeddedin" \
+          --data-urlencode "eititle=$tmpl" --data-urlencode "einamespace=0" \
+          --data-urlencode "eilimit=$n" |
+        jqp "import json,sys
+d=json.load(sys.stdin)
+if 'error' in d: sys.exit('NOT FOUND: '+d['error'].get('info',''))
+for m in d['query']['embeddedin']: print(m['title'])" |
+        while IFS= read -r title; do printf '%s\t%s\n' "$tmpl" "$title"; done >> "$results"
+    done
+    python3 - "$results" "$n" <<'PY'
+import sys
+from collections import OrderedDict
+
+path, limit_text = sys.argv[1:]
+limit = int(limit_text)
+groups = OrderedDict()
+seen = set()
+with open(path, encoding="utf-8") as handle:
+    for line in handle:
+        template, title = line.rstrip("\n").split("\t", 1)
+        if title in seen:
+            continue
+        seen.add(title)
+        groups.setdefault(template, []).append(title)
+        if len(seen) == limit:
+            break
+for template, titles in groups.items():
+    print(f"== {template} ==")
+    print("\n".join(titles))
+PY
+    ;;
   *)
-    sed -n '2,14p' "$0"; exit 1
+    sed -n '2,13p' "$0"; exit 1
     ;;
 esac

package/packages/software-development/wikipedia-uk-editor/adapters/codex/README.md

@@ -1,20 +1,50 @@
 # Codex Adapter for wikipedia-uk-editor
 
-This is a Codex-specific adapter for the `olko:wikipedia-uk-editor` skill.
-The canonical skill definition is in `../../SKILL.md`.
+Codex resolves this skill today via a symlink:
 
-## Usage
+```text
+~/.codex/skills/olko:wikipedia-uk-editor -> .../agent-skills/packages/software-development/wikipedia-uk-editor
+```
+
+`SKILL.md`, `references/`, and `scripts/` are all reachable through that symlink. Because it's a
+symlink and not a copy, any edit made to this package (this file included) reaches Codex
+immediately — no reinstall, no rebuild step.
+
+The canonical skill definition is `../../SKILL.md`.
 
-Invoke in a Codex session:
+## Requirements
+
+`curl` and `python3` — `scripts/wiki.sh` (the read-only MediaWiki API helper) shells out to both.
+See the `compatibility:` field in `../../SKILL.md`.
+
+## Invocation
 
 ```text
 Use the olko:wikipedia-uk-editor skill to draft a Ukrainian Wikipedia edit for <URL or title>.
 ```
 
+```text
+Use the olko:wikipedia-uk-editor skill: Легкі → Вичитувати on "<title>"
+```
+
+## Modes
+
+Classified from the input in `../../SKILL.md` §1:
+
+- **Translate** — en.wikipedia.org URL with no uk equivalent
+- **Expand** — uk stub or thin article
+- **Source** — uk article carrying `{{Без джерел}}` / `{{Джерело}}`
+- **Cleanup** — uk article with prose/format problems
+- **Plan** — "what should I edit next" → reads `references/strategy.md`
+
+Newcomer task types (`copyedit`, `links`, `references`, `update`, `expand`) route into these same
+modes but under a tighter, type-specific scope ceiling — see `references/newcomer-tasks.md` for
+the full mapping and what each type must not touch.
+
 ## Workflow
 
-See `../../SKILL.md` for the full workflow: classify the task (translate / expand / source /
-cleanup / plan), read the live wikitext through the read-only `scripts/wiki.sh` MediaWiki helper,
-gather and verify real sources, draft policy-compliant wikitext using the verified templates in
-`references/wikitext-uk.md`, run the self-check, and hand back ready-to-paste wikitext with a
-Ukrainian edit summary. The skill never saves an edit — the human pastes it.
+Resolve the title, read the live wikitext through `scripts/wiki.sh` (read-only), gather and
+verify real sources, draft policy-compliant wikitext using the verified templates in
+`references/wikitext-uk.md`, run the self-check in `../../SKILL.md` §5, and hand back
+ready-to-paste wikitext with a Ukrainian edit summary. The skill never saves an edit — the human
+pastes it.