@olegkoval/agent-skills 1.34.0 → 1.35.0

package/packages/software-development/review-past-performance/adapters/windsurf/rules/review-past-performance.md

@@ -1,200 +0,0 @@
-<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
-
----
-description: "Self-improvement loop that pulls the last 24h of ICM memories, git history, and skill analytics to detect repeated mistakes, slow workflows, and missing coverage, then proposes 1-3 concrete improvements."
----
-
-# /review-past-performance
-
-Self-improvement loop. Analyze recent sessions, find durable patterns, propose fixes.
-
-## Step 1 — Gather raw signals (run in parallel)
-
-```bash
-# A: ICM memories from last 24h
-icm recall "mistakes errors repeated workflow" --limit 10 2>/dev/null || echo "ICM_UNAVAILABLE"
-icm recall "completed task feature fix" --limit 10 2>/dev/null || echo "ICM_UNAVAILABLE"
-```
-
-```bash
-# B: Git activity last 24h across all repos the user works in
-git log --all --since="24 hours ago" --oneline --author="$(git config user.email 2>/dev/null)" 2>/dev/null | head -30 || echo "NO_GIT"
-```
-
-```bash
-# C: ICM transcripts (last 3 sessions)
-icm transcript search "" --limit 3 2>/dev/null || echo "TRANSCRIPTS_UNAVAILABLE"
-```
-
-```bash
-# D: Skill usage from gstack analytics (what skills were run, outcomes)
-tail -50 ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null | jq -c 'select(.ts > (now - 86400 | todate))' 2>/dev/null || \
-  tail -50 ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null | head -20 || echo "NO_ANALYTICS"
-```
-
-```bash
-# E: ICM errors-resolved topic (what broke and was fixed)
-icm recall "error" -t "errors-resolved" --limit 5 2>/dev/null || echo "NO_ERROR_MEMORIES"
-```
-
-```bash
-# F: Recent learnings (gstack)
-_GSTACK_HOME="${GSTACK_HOME:-$HOME/.gstack}"
-eval "$($HOME/.slate/skills/gstack/bin/gstack-slug 2>/dev/null)" 2>/dev/null || true
-_LEARN_FILE="$_GSTACK_HOME/projects/${SLUG:-unknown}/learnings.jsonl"
-[ -f "$_LEARN_FILE" ] && tail -20 "$_LEARN_FILE" || echo "NO_LEARNINGS"
-```
-
-## Step 2 — Synthesize patterns
-
-Read all signals. Classify findings into these categories:
-
-**Repeated mistakes** — same error, same fix, same confusion appearing more than once in the signals. E.g., always forgetting to handle null on a specific field, always hitting the same linting error.
-
-**Slow workflows** — multi-step sequences that took many tool calls but could be a single skill. E.g., always doing manual `git log` + `grep` + read 3 files before every PR review.
-
-**Missing coverage** — areas where work was done but no test was written or no memory was stored.
-
-**Underused skills** — skills that would have applied but were not invoked (check skill-usage.jsonl gaps vs. git activity).
-
-**Knowledge gaps** — concepts that came up repeatedly as questions or confusion.
-
-Score each finding:
-- **Frequency**: how many times it appeared (1 = once, 3 = three or more)
-- **Time cost**: rough estimate per occurrence (minutes)
-- **Fixability**: easy (a new skill/memory fixes it), medium (needs a process change), hard (structural)
-
-Pick the top 1-3 findings by `frequency × time_cost × fixability_inverse`.
-
-## Step 3 — Formulate proposals
-
-For each finding, produce exactly one proposal. Proposal types:
-
-**Type A — New skill**: The repeated sequence can be codified. Provide:
-- Proposed skill name (lowercase, dashes, ≤32 chars)
-- Trigger phrases (3-5)
-- 5-8 line SKILL.md workflow skeleton
-- Estimated time savings per occurrence
-
-**Type B — Skill tweak**: An existing skill is close but missing a step or check. Provide:
-- Which skill (`/skill-name`)
-- What specific text to add/change (before/after diff)
-- Why this covers the gap
-
-**Type C — ICM memory / eval criteria**: A pattern should be captured as a durable memory or eval rule. Provide:
-- `icm store` command (with topic, content, importance)
-- Or: a yes/no eval question to add to an existing skill
-
-## Step 4 — Present findings (D1)
-
-Use AskUserQuestion:
-
-```
-D1 — Performance review: N patterns found, N proposals
-Project/branch/task: 24h session review — git, ICM memories, skill analytics.
-ELI10: I looked at your last 24 hours of work: git commits, ICM memories,
-skill runs, and resolved errors. Here's what I found repeating and what
-I'd do about it. Approve proposals individually or skip any.
-Stakes if we pick wrong: skipping a proposal leaves the pattern unfixed;
-approving a bad proposal adds noise. You can always /skillify or rm a skill later.
-Recommendation: A — review each proposal and approve what resonates.
-Note: options differ in kind, not coverage — no completeness score.
-A) Walk me through each proposal (recommended)
-B) Show summary only, I'll decide what to dig into
-C) Abort — nothing to act on today
-```
-
-If B: print a one-line summary table (proposal number, type, finding, estimated savings). Stop.
-
-If C: print "No changes made. Run /review-past-performance again anytime." Stop.
-
-If A: proceed to Step 5.
-
-## Step 5 — Proposal gate (one per proposal)
-
-For each proposal (D2, D3, D4 ...):
-
-Print:
-```
---- Proposal N of N ---
-Finding: <one sentence>
-Pattern evidence: <which signals showed this>
-Proposal type: <A/B/C>
-<full proposal detail from Step 3>
-Estimated savings: ~X min/occurrence
-```
-
-Then AskUserQuestion:
-
-```
-D<N> — Apply proposal N: <short title>?
-Project/branch/task: <finding in one sentence>
-ELI10: <plain English: what this proposes, what changes, what you gain>
-Stakes if we pick wrong: <what happens if you apply a bad one, or skip a good one>
-Recommendation: A — apply it — the evidence is clear enough to try it.
-Note: options differ in kind, not coverage — no completeness score.
-A) Apply this proposal (recommended)
-B) Skip this one
-C) Modify before applying (describe what to change)
-```
-
-If C: ask what to change, update the proposal in-memory, re-show, re-ask A/B only.
-
-## Step 6 — Execute approved proposals
-
-For each approved proposal:
-
-**Type A (new skill):**
-```bash
-mkdir -p ~/.claude/skills/<name>
-```
-Write `~/.claude/skills/<name>/SKILL.md` with the skeleton from Step 3.
-Print: "Skill /<name> created at ~/.claude/skills/<name>/SKILL.md — invoke it with /<name>."
-
-**Type B (skill tweak):**
-Read the target skill file. Apply the diff. Print the before/after. Do NOT commit.
-
-**Type C (ICM memory):**
-```bash
-icm store -t "<topic>" -c "<content>" -i <importance> -k "<keywords>"
-```
-Print the stored memory ID.
-
-## Step 7 — Summary
-
-After all proposals are processed, print a compact summary:
-
-```
-/review-past-performance complete
-Applied: N proposals
-Skipped: N proposals
-
-What changed:
-- [list each applied change with one line]
-
-Run again tomorrow: /review-past-performance
-```
-
-Then:
-```bash
-# Store this review run as an ICM memory so future reviews have continuity
-icm store -t "context-workflow" \
-  -c "Performance review $(date +%Y-%m-%d): found [N] patterns, applied [N] proposals. Key findings: [one-line summary]" \
-  -i medium \
-  -k "performance-review,self-improvement" 2>/dev/null || true
-```
-
-```bash
-# Log to gstack timeline if available
-~/.slate/skills/gstack/bin/gstack-timeline-log \
-  '{"skill":"review-past-performance","event":"completed","outcome":"success"}' 2>/dev/null || true
-```
-
----
-
-## Notes
-
-- This skill reads only — no git mutations, no PR actions, no Notion/Linear writes.
-- Type A skills created here are skeletons. Run them once and tune before relying on them.
-- If ICM is unavailable (`ICM_UNAVAILABLE`), fall back to git log + gstack analytics only; note the limitation in findings.
-- If there are fewer than 3 signals available, say so and offer to run again after more sessions.

package/packages/software-development/self-critique/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-self-critique",
-  "description": "Adversarially critique your own last answer: spawn a critic agent that verifies claims against live sources, finds the related issue or pattern you missed, then loop until satisfied and report where you were wrong, iterations-to-satisfy, the numeric improvement, and a final score.",
-  "skills": "./skills"
-}

package/packages/software-development/self-critique/adapters/codex/README.md

@@ -1,21 +0,0 @@
-# Codex Adapter for self-critique
-
-This is a Codex-specific adapter for the `olko:self-critique` skill.
-The canonical skill definition is in `../../../SKILL.md`.
-
-## Usage
-
-Invoke in a Codex session:
-
-```
-Use the olko:self-critique skill to adversarially review your last answer and report a confidence score.
-```
-
-## Workflow
-
-See `../../../SKILL.md` for the full workflow: spawn a critic agent, verify every claim against live
-sources, find the related issue or pattern you missed, then loop (revise, re-score) until satisfied
-and report where you were wrong, iterations-to-satisfy, the numeric improvement, and a final score.
-
-The optional Claude Code `Stop` hook (`scripts/critique-nudge.mjs`) is Claude-specific and does not
-apply to Codex; the skill procedure itself is agent-agnostic.

package/packages/software-development/self-critique/adapters/cursor/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:self-critique",
-  "version": "0.1.0",
-  "description": "Adversarially critique your own last answer: spawn a critic agent that verifies claims against live sources, finds the related issue or pattern you missed, then loop until satisfied and report where you were wrong, iterations-to-satisfy, the numeric improvement, and a final score.",
-  "skills": "skills/"
-}

package/packages/software-development/self-critique/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:self-critique",
-  "version": "0.1.0",
-  "description": "Adversarially critique your own last answer: spawn a critic agent that verifies claims against live sources, finds the related issue or pattern you missed, then loop until satisfied and report where you were wrong, iterations-to-satisfy, the numeric improvement, and a final score.",
-  "skills": "skills/"
-}

package/packages/software-development/semantic-release-beta/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-semantic-release-beta",
-  "description": "Set up semantic-release-npm-github-publish with stable main releases and prerelease beta releases on a beta branch.",
-  "skills": "./skills"
-}

package/packages/software-development/semantic-release-beta/adapters/codex/README.md

@@ -1,3 +0,0 @@
-# Codex adapter
-
-Use the canonical skill directly from `packages/software-development/semantic-release-beta/SKILL.md`.

package/packages/software-development/semantic-release-beta/adapters/cursor/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:semantic-release-beta",
-  "version": "0.1.0",
-  "description": "Set up semantic-release-npm-github-publish with stable main releases and prerelease beta releases on a beta branch.",
-  "skills": "skills/"
-}

package/packages/software-development/semantic-release-beta/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:semantic-release-beta",
-  "version": "0.1.0",
-  "description": "Set up semantic-release-npm-github-publish with stable main releases and prerelease beta releases on a beta branch.",
-  "skills": "skills/"
-}

package/packages/software-development/semantic-release-beta/adapters/windsurf/rules/semantic-release-beta.md

@@ -1,46 +0,0 @@
-<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
-
----
-description: "Set up semantic-release-npm-github-publish with stable main releases and prerelease beta releases on a beta branch."
----
-
-# semantic-release-beta
-
-Use this skill when a project needs a reusable beta prerelease workflow with:
-
-- `semantic-release`
-- `semantic-release-npm-github-publish`
-- GitHub Actions
-- a stable `main` branch
-- a prerelease `beta` branch
-- npm publishing with `beta` prerelease versions
-- changelog generation, GitHub releases, npm publishing, and release commits through the maintained preset
-
-## Trigger phrases
-
-- add a beta release workflow
-- publish prereleases from a `beta` branch
-- set up `semantic-release` with `main` and `beta`
-- use `semantic-release-npm-github-publish`
-- add release validation or dry-run checks in CI
-
-## Workflow
-
-1. Inspect the repository first.
-2. Install or update `semantic-release`, `semantic-release-npm-github-publish`, and the peer plugins expected by the preset.
-3. Configure the repo-local semantic-release file to extend `semantic-release-npm-github-publish` and set branches explicitly:
-   - `main` for stable releases
-   - `{ name: "beta", channel: "beta", prerelease: "beta" }` for prereleases
-4. Add scripts if missing:
-   - `semantic-release`: `semantic-release`
-   - `release:dry-run`: `semantic-release --dry-run --no-ci`
-5. Update GitHub Actions to test both `main` and `beta`, validate npm auth, and run release dry-run before real releases.
-6. Preserve existing package manager and Node version policy unless the repo needs the preset's supported Node range.
-7. Use repo-local plugin composition instead of this preset only when the project needs different plugins, different release rules, or full control over plugin upgrade timing.
-
-## References
-
-- `references/preset.md`
-- `references/node-semantic-release.md`
-- `references/github-actions.md`
-- `references/validation.md`

package/packages/software-development/shared-knowledge-artifact/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-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 it, and publishes new versions of itself so several agents read the same lessons before working and append to them afterwards.",
-  "skills": "./skills"
-}

package/packages/software-development/skill-budget-audit/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-skill-budget-audit",
-  "description": "Diagnose and fix Claude Code skill context budget overflow — identify heavy plugin bundles, remove domain-specific ones, and restore skill discoverability.",
-  "skills": "./skills"
-}

package/packages/software-development/skill-budget-audit/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:skill-budget-audit",
-  "version": "0.1.0",
-  "description": "Diagnose and fix Claude Code skill context budget overflow — identify heavy plugin bundles, remove domain-specific ones, and restore skill discoverability.",
-  "skills": "skills/"
-}

package/packages/software-development/starter-rules/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-starter-rules",
-  "description": "Load and enforce hard rules for every oleg-koval/* starter: 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, no comments, KISS/DRY/SOLID.",
-  "skills": "./skills"
-}

package/packages/software-development/starter-rules/adapters/codex/README.md

@@ -1,16 +0,0 @@
-# Codex Adapter for starter-rules
-
-This is a Codex-specific adapter for the `olko:starter-rules` skill.
-The canonical skill definition is in `../../../SKILL.md`.
-
-## Usage
-
-Invoke in a Codex session:
-
-```
-Use the olko:starter-rules skill to load and enforce hard rules in this starter repo.
-```
-
-## Workflow
-
-See `../../../SKILL.md` for the full workflow.

package/packages/software-development/starter-rules/adapters/cursor/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:starter-rules",
-  "version": "0.1.0",
-  "description": "Load and enforce hard rules for every oleg-koval/* starter: 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, no comments, KISS/DRY/SOLID.",
-  "skills": "skills/"
-}

package/packages/software-development/starter-rules/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:starter-rules",
-  "version": "0.1.0",
-  "description": "Load and enforce hard rules for every oleg-koval/* starter: 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, no comments, KISS/DRY/SOLID.",
-  "skills": "skills/"
-}

package/packages/software-development/starter-rules/adapters/kiro/steering/starter-rules.md

@@ -1,61 +0,0 @@
-<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
-
----
-inclusion: manual
-description: "Load and enforce hard rules for every oleg-koval/* starter: 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, no comments, KISS/DRY/SOLID."
----
-
-# Starter Rules
-
-## Overview
-
-Load the canonical hard rules for every `oleg-koval/*` starter repo and verify the current repo complies with them. Produces a compliance report and a list of gaps to fix.
-
-## When to Use
-
-- Starting a new coding session in any `oleg-koval/*` template repo
-- Auditing an existing starter for rule compliance before a release or PR merge
-- Onboarding a new contributor (human or AI) to a starter
-- After a large refactor, to verify rules have not been silently violated
-
-Do not use for repos outside the `oleg-koval` namespace unless they explicitly reference `RULES.md`.
-
-## Workflow
-
-1. **Load the rules** — read `RULES.md` from the repo root. If absent, fetch it from `https://github.com/oleg-koval/starters/blob/main/RULES.md` and note that the starter is missing a local copy.
-
-2. **Apply §2 hard rules** — for the current task or PR diff, verify:
-   - No file exceeds 300 lines (`find . -name '*.ts' -o -name '*.py' -o -name '*.go' | xargs wc -l | awk '$1 > 300 && $2 != "total"'`)
-   - No functions produce side effects outside of boundary layers
-   - New code has no WHAT-comments; WHY-comments are one line max
-   - Tests are E2E-first; unit tests only for pure logic with non-trivial branching
-
-3. **Verify hooks and lint** — check that pre-commit hooks are installed and configured:
-   - TypeScript: `cat .eslintrc* | grep max-lines` and `cat package.json | grep -A5 '"lint-staged"\|"husky"\|"lefthook"'`
-   - Python: `cat .pre-commit-config.yaml` and check for `ruff` + format hooks
-   - Go: `cat .golangci.yml` or `.pre-commit-config.yaml` and check for `golangci-lint` + `gofmt`
-
-4. **Check architecture** — for app/SaaS starters: confirm feature code is organized as vertical slices (feature directory contains handler + DTO + service + tests together). For library starters: skip.
-
-5. **Report gaps** — list any violations found in steps 2–4. For each gap:
-   - Name the rule (e.g., "§2.2 file length")
-   - Name the file and line count or violation
-   - Propose the minimal fix
-
-6. **Fix on request** — if the user asks to fix the gaps, apply them one at a time, smallest change first. Do not refactor beyond what the rule requires.
-
-## Reference
-
-Full rule details: [`RULES.md`](./RULES.md)
-
-Architecture options and future starters: `RULES.md §3`
-
-Unix principles: `RULES.md §4`
-
-## Verification
-
-- [ ] `RULES.md` was read from the repo root (or fetched and absence noted)
-- [ ] File length check ran with zero violations, or violations were listed
-- [ ] Pre-commit hooks verified as installed and configured
-- [ ] Compliance report produced listing passed checks and gaps
-- [ ] Any fixes applied do not exceed the scope of the violated rule

package/packages/software-development/store-listing-copy/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-store-listing-copy",
-  "description": "Generate platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog or release notes.",
-  "skills": "./skills"
-}

package/packages/software-development/store-listing-copy/adapters/codex/README.md

@@ -1,20 +0,0 @@
-# Codex Adapter for store-listing-copy
-
-This is a Codex-specific adapter for the `olko:store-listing-copy` skill.
-The canonical skill definition is in `../../SKILL.md`.
-
-## Usage
-
-Invoke in a Codex session:
-
-```text
-Use the olko:store-listing-copy skill to generate App Store listing copy for the next release.
-```
-
-## Workflow
-
-See `../../SKILL.md` for the full workflow: read app metadata and git changelog, classify
-changes by user impact, draft platform-specific copy fields (title, subtitle, description,
-what's new, keywords) within each platform's character limits, validate against store
-policy rules, and write the output to a scratch file for human review and paste. Supports
-iOS App Store, Google Play, and Garmin Connect IQ. The procedure is agent-agnostic.

package/packages/software-development/store-listing-copy/adapters/cursor/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:store-listing-copy",
-  "version": "0.1.0",
-  "description": "Generate platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog or release notes.",
-  "skills": "skills/"
-}

package/packages/software-development/store-listing-copy/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:store-listing-copy",
-  "version": "0.1.0",
-  "description": "Generate platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog or release notes.",
-  "skills": "skills/"
-}

package/packages/software-development/vinted-listing/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-vinted-listing",
-  "description": "Create, edit, and safely publish Vinted listings through the signed-in browser, using verified item details and the owner’s original photos.",
-  "skills": "./skills"
-}

package/packages/software-development/vinted-listing/adapters/codex/README.md

@@ -1,3 +0,0 @@
-# Codex adapter
-
-Use the canonical skill directly from `packages/software-development/vinted-listing/SKILL.md`.

package/packages/software-development/vinted-listing/adapters/cursor/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:vinted-listing",
-  "version": "0.1.0",
-  "description": "Create, edit, and safely publish Vinted listings through the signed-in browser, using verified item details and the owner’s original photos.",
-  "skills": "skills/"
-}

package/packages/software-development/vinted-listing/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:vinted-listing",
-  "version": "0.1.0",
-  "description": "Create, edit, and safely publish Vinted listings through the signed-in browser, using verified item details and the owner’s original photos.",
-  "skills": "skills/"
-}

package/packages/software-development/wikipedia-uk-editor/adapters/claude/plugin.json

@@ -1,5 +0,0 @@
-{
-  "name": "olko-wikipedia-uk-editor",
-  "description": "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary.",
-  "skills": "./skills"
-}

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

@@ -1,50 +0,0 @@
-# Codex Adapter for wikipedia-uk-editor
-
-Codex resolves this skill today via a symlink:
-
-```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`.
-
-## 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
-
-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.

package/packages/software-development/wikipedia-uk-editor/adapters/cursor/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:wikipedia-uk-editor",
-  "version": "0.1.0",
-  "description": "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary.",
-  "skills": "skills/"
-}

package/packages/software-development/wikipedia-uk-editor/adapters/grok/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "olko:wikipedia-uk-editor",
-  "version": "0.1.0",
-  "description": "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary.",
-  "skills": "skills/"
-}

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

@@ -1,3 +0,0 @@
-# Hermes adapter
-
-Use the canonical skill directly from `packages/software-development/wikipedia-uk-editor/SKILL.md`.

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

@@ -1,3 +0,0 @@
-# Pi adapter
-
-Use the canonical skill directly from `packages/software-development/wikipedia-uk-editor/SKILL.md`.