Match rtb skill frontmatter (effort + argument-hint) for / menu visibility

Symptom: typing /dev-loop shows no skills in the typeahead, while /rtb shows all
of rtb's. Comparing the installed rtb plugin (dev-rsquare/rtb-ai) against dev-loop:
every rtb skill carries `effort:` (35/35) and most carry `argument-hint:` (a
slash-command frontmatter field the docs describe as "shown to the user when
auto-completing the slash command"); dev-loop skills had only name + description.

Add `effort` and `argument-hint` to all 8 skills, matching rtb's pattern, so CC
indexes them as slash-completable entries under the /dev-loop namespace.

Best-guess fix aligned to the rtb reference — needs update + restart to verify.
Bump 0.7.0 -> 0.8.0.

Author: choiyounggi

.claude-plugin/marketplace.json

@@ -20,7 +20,7 @@
         "url": "https://github.com/choiyounggi/dev-loop.git"
       },
       "homepage": "https://github.com/choiyounggi/dev-loop",
-      "version": "0.7.0",
+      "version": "0.8.0",
       "tags": [
         "orchestrator",
         "verification-loop",

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "dev-loop",
   "description": "loop-orchestrator's verification loop (TDD / PDCA / Reflexion) with the plan step FIXED to a wiki-grounded planning methodology (wiki-plan): every design decision is routed to a bundled semantic-layer wiki before code is written. Adds a knowledge-capture loop — sessions emit verified insights, and knowledge-flush researches, dedups, routes, and opens a wiki PR for owner review.",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "author": {
     "name": "choiyounggi",
     "url": "https://github.com/choiyounggi"

skills/configure/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: configure
+effort: medium
+argument-hint: "[global | repo]"
 description: Set up dev-loop's capability-role tool profile — map `knowledge` (your domain wiki / MCP), `verify` (your project's test/build/QA command), `explore` (code search), `tacit` (past incidents), and `design` (Figma/visual spec) to the actual tools this environment has, then write ~/.claude/dev-loop/tools.json (global) or <repo>/.dev-loop/tools.json (per-repo). Use when asked to "configure dev-loop", "set up tools", "map my wiki/test command", or "/dev-loop:configure".
 ---
 

skills/knowledge-flush/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: knowledge-flush
+effort: high
+argument-hint: "[optional: filters]"
 description: Drain queued ★ Insight candidates (harvested from your sessions) into the wiki as a reviewed PR. For each candidate it researches and verifies the best-practice against real sources, checks existing wiki layers for duplicates and links, decides the target layer/category (or justifies a new one), runs wiki-ingest, then opens ONE PR per flush for you to review and merge/reject. Never auto-merges. Use when asked to "flush knowledge", "process the insight queue", "ingest what I learned", or "/dev-loop:knowledge-flush".
 ---
 

skills/loop-implement/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: loop-implement
+effort: high
+argument-hint: "[task or feature to build]"
 description: The single implementation loop. It plans via wiki-plan (step 2, required) into an ordered, wiki-navigated task list, then executes those tasks in order, each loading only its named wiki pages, writing tests first, getting an independent test-quality audit, and judging against done; on failure it reflects and retries (bounded). Use for a non-trivial task or feature. Skip typos, config values, and simple renames.
 ---
 

skills/orchestrate/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: orchestrate
+effort: high
+argument-hint: "[goal or parent issue]"
 description: Orchestrate one natural-language goal into parallel tmux Claude Code sessions. It decomposes the goal (with your approval), plans each task with wiki-plan, implements and reviews, runs an integration test, and merges after your confirmation. Use to build a goal across multiple sessions. For a single task, use loop-implement instead.
 ---
 

skills/wiki-ingest/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: wiki-ingest
+effort: medium
+argument-hint: "[the lesson or edge case]"
 description: Add one verified lesson or edge case to the bundled wiki. Route it to the right domain and category, merge into an existing page before creating a new one, and enforce sourcing and positive-guidance rules. Use when capturing a documented best practice or a production edge case.
 ---
 

skills/wiki-lint/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: wiki-lint
+effort: medium
+argument-hint: "[optional: changed pages]"
 description: Health-check the bundled wiki. Detect unsourced claims, bare prohibitions, broken links, index and page trigger mismatches, vague qualifiers, oversized pages, and stale dates, then fix them. Use to keep the wiki healthy before drift compounds.
 ---
 

skills/wiki-plan/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: wiki-plan
+effort: high
+argument-hint: "[what to build]"
 description: The fixed planning methodology for a capable model. Make every design decision grounded in a bundled wiki page (recording a decision-to-page map), then decompose the work into ordered, self-contained tasks, each naming the exact wiki pages that govern it. Runs as loop-implement step 2.
 ---
 

skills/wiki-query/SKILL.md

@@ -1,5 +1,7 @@
 ---
 name: wiki-query
+effort: medium
+argument-hint: "[your question]"
 description: Answer a development question from the wiki with citations, loading only the pages whose triggers match. If the answer required synthesis across multiple pages and the question is likely to recur, file the synthesis back as a new page so knowledge compounds.
 ---