@rune-kit/rune 2.8.0 → 2.11.0

package/extensions/chrome-ext/skills/cws-publish.md

@@ -1,104 +1,104 @@
----
-name: "cws-publish"
-pack: "@rune/chrome-ext"
-description: "Chrome Web Store listing preparation and submission guide — store listing copy, screenshot descriptions, permission justifications, visibility settings, and timeline expectations."
-model: sonnet
-tools: [Read, Edit, Write, Grep, Glob, Bash]
----
-
-# cws-publish
-
-Chrome Web Store listing preparation and submission guide — store listing copy, screenshot descriptions, permission justifications, visibility settings, and timeline expectations. Produces a ready-to-paste store listing document.
-
-#### Workflow
-
-**Step 1 — Verify preflight passed**
-Check for `.rune/chrome-ext/preflight-report.md`. If it does not exist or contains FAIL items, halt and direct user to run `cws-preflight` first. WARN items should be reviewed and resolved before submission.
-
-**Step 2 — Prepare store listing copy**
-Generate CWS listing text following Google's constraints:
-- **Name**: max 45 characters. Must not include trademarked names (Google, Chrome, YouTube, Gmail). Cannot include "Extension" (Chrome adds it automatically).
-- **Short description**: max 132 characters. First thing users see in search results — front-load the value proposition.
-- **Detailed description**: no hard limit but 400–800 words is optimal. Structure: opening hook (1 sentence) → feature bullets (5-7) → how it works (2-3 sentences) → privacy statement (1-2 sentences).
-- Avoid keyword stuffing — Google's policy considers it spam.
-
-**Step 3 — Generate screenshot descriptions**
-CWS screenshots need captions (optional but recommended). Generate 3-5 screenshot scenarios showing distinct use cases. Each screenshot should be 1280×800 or 640×400 pixels, PNG or JPEG, <2MB.
-
-**Step 4 — Fill permission justifications**
-Pull from `cws-preflight` output. Each permission needs a one-paragraph justification in plain English. Write from the user's perspective: "This permission allows the extension to..." not "We need this to...".
-
-**Step 5 — Choose visibility and distribution**
-| Visibility | Use Case |
-|------------|----------|
-| Public | Visible in CWS search — default for most extensions |
-| Unlisted | Direct URL only — good for beta testing with known users |
-| Private | Team-only — enterprise internal tools |
-
-Select distribution regions (default: all). Consider unlisted for v1.0 while gathering initial feedback, then switch to public after first positive reviews.
-
-**Step 6 — Generate submission guide with timeline**
-Emit `.rune/chrome-ext/store-listing.md` with all copy ready to paste. Include submission steps and timeline expectations.
-
-**Timeline expectations:**
-- Simple extension, experienced developer account, no sensitive permissions: **24–72 hours**
-- Sensitive permissions (`tabs`, `history`, `cookies`, `management`): **3–7 business days**
-- Broad `host_permissions` or first submission: **up to 3 weeks** (manual review queue)
-- Rejection: **10-day resubmission window** after fixing issues; same review time applies
-
-**Submission tips:**
-- Never submit on Friday — reviewers are less available Mon-Tue; submit Tue-Thu
-- Use `optional_permissions` for non-critical features — reduces barrier to install and CWS scrutiny
-- `optional_host_permissions` can be requested at runtime, reducing declared permissions
-- Version bump required for each resubmission after rejection
-- Include a test account in submission notes if extension requires authentication
-
-#### Example
-
-```markdown
-<!-- .rune/chrome-ext/store-listing.md (generated by cws-publish) -->
-
-# CWS Store Listing — Page Summarizer
-
-## Name (max 45 chars)
-Page Summarizer — AI-Powered Summaries
-(38 chars ✅)
-
-## Short Description (max 132 chars)
-Summarize any webpage instantly with built-in Chrome AI. One click, no account required, no data sent externally.
-(113 chars ✅)
-
-## Detailed Description
-Tired of spending 10 minutes reading a page to find out it wasn't worth your time?
-
-**Page Summarizer** gives you the core ideas of any webpage in seconds — powered by Chrome's built-in Gemini Nano model, which runs entirely on your device.
-
-**Features:**
-- One-click summarization — click the toolbar button or select text to summarize a section
-- Built-in AI — no API key required, no data leaves your device (requires Chrome 138+ with AI hardware support)
-- External API fallback — configure your own OpenAI or Anthropic key for older hardware
-- Summary length control — short (100 words), medium (300 words), or detailed (500 words)
-- Side panel view — summaries appear in a non-intrusive panel alongside the page
-- Dark mode support
-
-**How it works:**
-Click the toolbar button on any page. The extension reads the visible text and generates a summary using the on-device Gemini Nano model. If your hardware does not support built-in AI, the extension falls back to an external API of your choice (optional — extension still works without it in built-in AI mode).
-
-**Privacy:**
-No user data is collected, stored, or transmitted without your action. Summaries generated via the built-in AI model never leave your device. External API calls (if configured) are made directly to the API provider — not through any intermediary server.
-
-## Screenshots (1280x800px)
-
-1. **Main Use** — Extension sidebar showing a 3-paragraph summary of a news article beside the original page.
-2. **Settings** — Settings panel showing AI model selector, API key field, and length preference.
-3. **Text Selection** — Right-click context menu on selected text showing "Summarize selection" option.
-
-## Category
-Productivity
-
-## Language
-English
-
-## Submission Notes (visible to reviewers, not users)
-Test the extension on https://en.wikipedia.org/wiki/Artificial_intelligence — click the toolbar button to summarize. The extension requires Chrome 138+ for built-in AI. On older Chrome versions, configure an external API key in Settings to test the fallback path.
-```
+---
+name: "cws-publish"
+pack: "@rune/chrome-ext"
+description: "Chrome Web Store listing preparation and submission guide — store listing copy, screenshot descriptions, permission justifications, visibility settings, and timeline expectations."
+model: sonnet
+tools: [Read, Edit, Write, Grep, Glob, Bash]
+---
+
+# cws-publish
+
+Chrome Web Store listing preparation and submission guide — store listing copy, screenshot descriptions, permission justifications, visibility settings, and timeline expectations. Produces a ready-to-paste store listing document.
+
+#### Workflow
+
+**Step 1 — Verify preflight passed**
+Check for `.rune/chrome-ext/preflight-report.md`. If it does not exist or contains FAIL items, halt and direct user to run `cws-preflight` first. WARN items should be reviewed and resolved before submission.
+
+**Step 2 — Prepare store listing copy**
+Generate CWS listing text following Google's constraints:
+- **Name**: max 45 characters. Must not include trademarked names (Google, Chrome, YouTube, Gmail). Cannot include "Extension" (Chrome adds it automatically).
+- **Short description**: max 132 characters. First thing users see in search results — front-load the value proposition.
+- **Detailed description**: no hard limit but 400–800 words is optimal. Structure: opening hook (1 sentence) → feature bullets (5-7) → how it works (2-3 sentences) → privacy statement (1-2 sentences).
+- Avoid keyword stuffing — Google's policy considers it spam.
+
+**Step 3 — Generate screenshot descriptions**
+CWS screenshots need captions (optional but recommended). Generate 3-5 screenshot scenarios showing distinct use cases. Each screenshot should be 1280×800 or 640×400 pixels, PNG or JPEG, <2MB.
+
+**Step 4 — Fill permission justifications**
+Pull from `cws-preflight` output. Each permission needs a one-paragraph justification in plain English. Write from the user's perspective: "This permission allows the extension to..." not "We need this to...".
+
+**Step 5 — Choose visibility and distribution**
+| Visibility | Use Case |
+|------------|----------|
+| Public | Visible in CWS search — default for most extensions |
+| Unlisted | Direct URL only — good for beta testing with known users |
+| Private | Team-only — enterprise internal tools |
+
+Select distribution regions (default: all). Consider unlisted for v1.0 while gathering initial feedback, then switch to public after first positive reviews.
+
+**Step 6 — Generate submission guide with timeline**
+Emit `.rune/chrome-ext/store-listing.md` with all copy ready to paste. Include submission steps and timeline expectations.
+
+**Timeline expectations:**
+- Simple extension, experienced developer account, no sensitive permissions: **24–72 hours**
+- Sensitive permissions (`tabs`, `history`, `cookies`, `management`): **3–7 business days**
+- Broad `host_permissions` or first submission: **up to 3 weeks** (manual review queue)
+- Rejection: **10-day resubmission window** after fixing issues; same review time applies
+
+**Submission tips:**
+- Never submit on Friday — reviewers are less available Mon-Tue; submit Tue-Thu
+- Use `optional_permissions` for non-critical features — reduces barrier to install and CWS scrutiny
+- `optional_host_permissions` can be requested at runtime, reducing declared permissions
+- Version bump required for each resubmission after rejection
+- Include a test account in submission notes if extension requires authentication
+
+#### Example
+
+```markdown
+<!-- .rune/chrome-ext/store-listing.md (generated by cws-publish) -->
+
+# CWS Store Listing — Page Summarizer
+
+## Name (max 45 chars)
+Page Summarizer — AI-Powered Summaries
+(38 chars ✅)
+
+## Short Description (max 132 chars)
+Summarize any webpage instantly with built-in Chrome AI. One click, no account required, no data sent externally.
+(113 chars ✅)
+
+## Detailed Description
+Tired of spending 10 minutes reading a page to find out it wasn't worth your time?
+
+**Page Summarizer** gives you the core ideas of any webpage in seconds — powered by Chrome's built-in Gemini Nano model, which runs entirely on your device.
+
+**Features:**
+- One-click summarization — click the toolbar button or select text to summarize a section
+- Built-in AI — no API key required, no data leaves your device (requires Chrome 138+ with AI hardware support)
+- External API fallback — configure your own OpenAI or Anthropic key for older hardware
+- Summary length control — short (100 words), medium (300 words), or detailed (500 words)
+- Side panel view — summaries appear in a non-intrusive panel alongside the page
+- Dark mode support
+
+**How it works:**
+Click the toolbar button on any page. The extension reads the visible text and generates a summary using the on-device Gemini Nano model. If your hardware does not support built-in AI, the extension falls back to an external API of your choice (optional — extension still works without it in built-in AI mode).
+
+**Privacy:**
+No user data is collected, stored, or transmitted without your action. Summaries generated via the built-in AI model never leave your device. External API calls (if configured) are made directly to the API provider — not through any intermediary server.
+
+## Screenshots (1280x800px)
+
+1. **Main Use** — Extension sidebar showing a 3-paragraph summary of a news article beside the original page.
+2. **Settings** — Settings panel showing AI model selector, API key field, and length preference.
+3. **Text Selection** — Right-click context menu on selected text showing "Summarize selection" option.
+
+## Category
+Productivity
+
+## Language
+English
+
+## Submission Notes (visible to reviewers, not users)
+Test the extension on https://en.wikipedia.org/wiki/Artificial_intelligence — click the toolbar button to summarize. The extension requires Chrome 138+ for built-in AI. On older Chrome versions, configure an external API key in Settings to test the fallback path.
+```