elliot-stack 1.0.24 → 1.0.27

package/README.md

@@ -11,7 +11,7 @@ A curated set of Claude Code skills by Elliot Drel. One command installs them al
 npx elliot-stack@latest
 ```
 
-This installs skills to `~/.agents/skills/` and symlinks them into `~/.claude/skills/`, then registers a `SessionStart` hook so your skills stay up to date automatically.
+This installs skills to `~/.agents/skills/` and symlinks them into `~/.claude/skills/`, then registers a `SessionStart` hook so your skills stay up to date automatically. Any agent that reads from `~/.agents/skills/` (OpenClaw, Codex, ChatGPT, Cursor, and others) will pick them up automatically with no extra config.
 
 ## Skills
 
@@ -32,11 +32,15 @@ This installs skills to `~/.agents/skills/` and symlinks them into `~/.claude/sk
 
 Hooks install to `~/.claude/hooks/` and are auto-registered in your `~/.claude/settings.json`.
 
+Important: hooks are a Claude Code feature. Skills are stored in `~/.agents/skills/`
+and linked into Claude, but hook scripts and hook registration can only be installed
+in Claude's config (`~/.claude/hooks/` and `~/.claude/settings.json`).
+
 ## How it works
 
-- Skills install to `~/.agents/skills/estack-*/` (symlinked from `~/.claude/skills/estack-*/`)
-- Hooks install to `~/.claude/hooks/` and are registered in `~/.claude/settings.json`
-- A `SessionStart` hook auto-updates both each time you open Claude Code
+- Skills install to `~/.agents/skills/estack-*/` (symlinked from `~/.claude/skills/estack-*/`; auto-detected by any agent that reads `~/.agents/skills/`, including OpenClaw, Codex, ChatGPT, and Cursor)
+- Hooks are Claude Code-only: they install to `~/.claude/hooks/` and are registered in `~/.claude/settings.json`
+- A `SessionStart` hook auto-updates skills each time you open Claude Code
 - If you've made local edits to a skill or hook, the installer detects the conflict and lets you choose: overwrite, skip, or merge
 - Every skill carries its own semver (`version:` in SKILL.md frontmatter; hooks use a `// @version` comment), independent of the package version — update messages show exactly what moved, e.g. `estack-chris-voss (1.0.0 → 1.1.0)`. Under the hood, updates are detected by content hash, so a change can never be missed; a release-time check (`scripts/check-versions.cjs`) guarantees every content change ships with a version bump.
 
@@ -50,7 +54,7 @@ npx elliot-stack@latest
 
 ## Requirements
 
-- [Claude Code](https://claude.ai/code) CLI installed
+- [Claude Code](https://claude.ai/code) CLI installed (other agents that read `~/.agents/skills/` work too)
 - Node.js 18+
 
 ## Contributing

package/bin/install.cjs

@@ -885,13 +885,13 @@ async function main() {
   // 11. Summary output
   if (DRY_RUN) {
     console.log('\n[dry run] No files were changed. Run with --install to apply.\n');
-    console.log('  ' + installedCount + ' skill' + (installedCount !== 1 ? 's' : '') + ' would be installed/updated in ~/.agents/skills/ (linked from ~/.claude/skills/)');
+    console.log('  ' + installedCount + ' skill' + (installedCount !== 1 ? 's' : '') + ' would be installed/updated in ~/.agents/skills/ (linked from ~/.claude/skills/; auto-detected by any agent that reads ~/.agents/skills/)');
     if (installedHookCount > 0) {
       console.log('  ' + installedHookCount + ' hook' + (installedHookCount !== 1 ? 's' : '') + ' would be installed/updated in ~/.claude/hooks/');
     }
   } else {
     console.log('\nestack installed successfully!\n');
-    console.log('  ' + installedCount + ' skill' + (installedCount !== 1 ? 's' : '') + ' installed to ~/.agents/skills/ (symlinked from ~/.claude/skills/)');
+    console.log('  ' + installedCount + ' skill' + (installedCount !== 1 ? 's' : '') + ' installed to ~/.agents/skills/ (symlinked from ~/.claude/skills/; auto-detected by any agent that reads ~/.agents/skills/)');
     if (installedHookCount > 0) {
       console.log('  ' + installedHookCount + ' hook' + (installedHookCount !== 1 ? 's' : '') + ' installed to ~/.claude/hooks/');
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "elliot-stack",
-  "version": "1.0.24",
+  "version": "1.0.27",
   "description": "Elliot's skill stack for Claude Code — install via npx elliot-stack@latest",
   "bin": {
     "elliot-stack": "bin/install.cjs"

package/skills/estack-active-learning-tutor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-active-learning-tutor
-version: 1.0.0
+version: 1.0.2
 description: (active-learning-tutor) Tutors a student through exam preparation using active learning — questioning, gap diagnosis, and concept mastery tracking. Use when the student says they want to study, learn, prep for an exam, be quizzed on a chapter, work through a practice test together, or be taught a topic conceptually rather than lectured.
 disable-model-invocation: true
 ---
@@ -339,40 +339,6 @@ When in doubt about the shape of a Teaching turn, read `references/teaching-turn
 
 ---
 
-## Skill Feedback
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-active-learning-tutor: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
-**If `gh` is not installed**, build a pre-filled URL:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-active-learning-tutor: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user and offer to open it in their browser.
-
-They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
-
----
-
 ## Skill Feedback
 
 If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:

package/skills/estack-better-title/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-better-title
-version: 1.0.0
+version: 1.0.2
 description: (better-title) Suggest better chat session titles and rename the session
 disable-model-invocation: true
 allowed-tools: Bash, AskUserQuestion
@@ -77,69 +77,6 @@ gh issue create \
   --body "<description from user feedback — expected vs. actual behavior and context>"
 ```
 
-**If `gh` is not installed**, build a pre-filled URL and share it so the user can click, review, and submit:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-better-title: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user. They click it, review the pre-filled title and body, then click **Submit new issue**.
-
----
-
-## Skill Feedback
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-better-title: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
-**If `gh` is not installed**, build a pre-filled URL:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-better-title: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user and offer to open it in their browser.
-
-They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
-
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-better-title: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
 **If `gh` is not installed**, build a pre-filled URL:
 
 ```bash

package/skills/estack-chris-voss/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-chris-voss
-version: 1.0.0
+version: 1.0.2
 description: >
   (chris-voss) Applies Chris Voss negotiation principles from *Never Split the Difference* to any situation
   where understanding human psychology, persuasion, or influence would improve the output. Use
@@ -93,69 +93,6 @@ gh issue create \
   --body "<description from user feedback — expected vs. actual behavior and context>"
 ```
 
-**If `gh` is not installed**, build a pre-filled URL and share it so the user can click, review, and submit:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-chris-voss: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user. They click it, review the pre-filled title and body, then click **Submit new issue**.
-
----
-
-## Skill Feedback
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-chris-voss: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
-**If `gh` is not installed**, build a pre-filled URL:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-chris-voss: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user and offer to open it in their browser.
-
-They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
-
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-chris-voss: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
 **If `gh` is not installed**, build a pre-filled URL:
 
 ```bash

package/skills/estack-customer-discovery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-customer-discovery
-version: 1.0.0
+version: 1.0.2
 description: (customer-discovery) Guide users through customer discovery — validating business ideas, identifying target customers, crafting outreach, preparing interview questions, and analyzing interview results. Use this skill whenever the user mentions customer discovery, customer interviews, validating an idea, market research, finding product-market fit, talking to customers, outreach messages, interview guides, or analyzing customer feedback. Also use when someone says they have a business idea and want to test it, or when they're preparing to talk to potential customers.
 ---
 
@@ -73,69 +73,6 @@ gh issue create \
   --body "<description from user feedback — expected vs. actual behavior and context>"
 ```
 
-**If `gh` is not installed**, build a pre-filled URL and share it so the user can click, review, and submit:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-customer-discovery: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user. They click it, review the pre-filled title and body, then click **Submit new issue**.
-
----
-
-## Skill Feedback
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-customer-discovery: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
-**If `gh` is not installed**, build a pre-filled URL:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-customer-discovery: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user and offer to open it in their browser.
-
-They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
-
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-customer-discovery: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
 **If `gh` is not installed**, build a pre-filled URL:
 
 ```bash

package/skills/estack-flight-planner/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-flight-planner
-version: 1.0.0
+version: 1.0.2
 description: (flight-planner) Find and rank flights between any two airports with config-driven preferences (budget, airlines, nonstop, time-of-day) and optional ground-shuttle pairing. Uses SerpAPI Google Flights (or WebSearch fallback). Saves preferences to `~/.flight-planner/config.json` and logs every search.
 disable-model-invocation: true
 ---
@@ -334,74 +334,6 @@ If the user doesn't have a SerpAPI key and asks for help getting one:
 
 ## Skill Feedback
 
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then build a pre-filled GitHub issue URL and share it so the user can click, review, and submit:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-flight-planner: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user. They click it, review the pre-filled title and body, then click **Submit new issue**.
-
-## Adding a shuttle service to your config
-
-If you regularly use a shuttle to your airport, add it to your config so the skill pairs flights with shuttle runs automatically:
-
-```json
-"shuttle_service": {
-  "name": "Your Shuttle Co.",
-  "schedule_urls": ["https://yourshuttle.example.com/schedule"],
-  "costs": {"ORD": 60, "MDW": 55},
-  "home_timezone": "America/New_York",
-  "airport_timezones": {"ORD": "America/Chicago", "MDW": "America/Chicago"}
-}
-```
-
-See `references/shuttle_schedules.md` for the full schema, JSON format the pairing script expects, and tips on extracting schedule data from a shuttle company's website.
-
----
-
-## Skill Feedback
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-flight-planner: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
-**If `gh` is not installed**, build a pre-filled URL:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-flight-planner: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user and offer to open it in their browser.
-
-They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
-
----
-
-## Skill Feedback
-
 If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
 
 **If `gh` is installed** (`gh --version` succeeds), create the issue directly:

package/skills/estack-github-issue-tracker/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-github-issue-tracker
-version: 1.0.0
+version: 1.0.2
 description: >
   (github-issue-tracker) GitHub issue tracker management. Checks all open issues the user is involved in,
   finds related/duplicate issues, reports what changed, and recommends next steps.
@@ -324,58 +324,6 @@ $ARGUMENTS
 
 ## Skill Feedback
 
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then build a pre-filled GitHub issue URL and share it so the user can click, review, and submit:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-github-issue-tracker: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user. They click it, review the pre-filled title and body, then click **Submit new issue**.
-
----
-
-## Skill Feedback
----
-
-## Skill Feedback
-
-If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
-
-**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
-
-```bash
-gh issue create \
-  --repo ElliotDrel/e-stack \
-  --title "estack-github-issue-tracker: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
-**If `gh` is not installed**, build a pre-filled URL:
-
-```bash
-python3 -c "
-import urllib.parse
-title = 'estack-github-issue-tracker: <concise summary>'
-body = '<description from user feedback — expected vs. actual behavior and context>'
-base = 'https://github.com/ElliotDrel/e-stack/issues/new'
-print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
-"
-```
-
-Share the printed URL with the user and offer to open it in their browser.
-
-They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
-
----
-
-## Skill Feedback
-
 If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
 
 **If `gh` is installed** (`gh --version` succeeds), create the issue directly:

package/skills/estack-prompt-builder-coach/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-prompt-builder-coach
-version: 1.0.0
+version: 1.0.2
 description: (prompt-builder-coach) Use whenever you or the user need to write, sharpen, audit, or scope a prompt or work request for an AI agent or model. This is a four-part kit covering shaping a fuzzy idea into a decided goal, building a prompt from scratch, auditing a draft request that feels vague, and defining what "done" looks like when the task is fuzzy. Trigger when the user says "help me write a prompt", "build me a prompt", "audit this prompt", "make this request better", "why is the AI giving me generic output", "I don't know what I want", "I have a rough idea", "what should done look like", or when handing a task to another agent and wanting it to land. Use it even when the user did not say the word "prompt" but is clearly trying to get an AI to do consequential work. Do not use for quick factual lookups or for executing an already well-defined task.
 ---
 
@@ -79,3 +79,33 @@ Every finished prompt or brief gets saved to a markdown file with a descriptive
 - Do not run a part from memory. Always read its file on entry, per Rule 1.
 - Do not over-apply the kit. A quick ask gets a quick prompt, not a six-field brief.
 </guardrails>
+---
+
+## Skill Feedback
+
+If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
+
+**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
+
+```bash
+gh issue create \
+  --repo ElliotDrel/e-stack \
+  --title "estack-prompt-builder-coach: <concise summary>" \
+  --body "<description from user feedback — expected vs. actual behavior and context>"
+```
+
+**If `gh` is not installed**, build a pre-filled URL:
+
+```bash
+python3 -c "
+import urllib.parse
+title = 'estack-prompt-builder-coach: <concise summary>'
+body = '<description from user feedback — expected vs. actual behavior and context>'
+base = 'https://github.com/ElliotDrel/e-stack/issues/new'
+print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
+"
+```
+
+Share the printed URL with the user and offer to open it in their browser.
+
+They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.

package/skills/estack-read-claude-session-history/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-read-claude-session-history
-version: 1.0.0
+version: 1.0.2
 description: (read-claude-session-history) Invoke for ANY task involving Claude Code session history, transcripts, or .jsonl files — this is the only way to read, parse, or search them; do not attempt to use Bash or Read on .jsonl directly. Use for: recovering context after /compact ("what were we doing before compact"), advisor response retrieval ("what did the advisor say"), subagent output collection ("get all subagent finals"), cross-project session search by keyword, session listing and triage, UUID and title lookup, resume-command generation, file-edit and tool-call forensics, session diff between two sessions or subagents, weekly work journal, day timeline of activity blocks and idle gaps, engagement/attention-time accounting (active vs elapsed time, break detection, parallel-chat-safe totals), recovering from .claude-backups after data loss, session count queries, and reading the last agent message before a crash or interrupt. Trigger phrases: "session history", "before compact", "what did claude do", "what did I work on", "search my sessions", "find that session", "what did the advisor say", "what did the agent edit", "from the backup", "list my sessions", "subagent outputs", "session journal", "resume previous", "which files did claude touch", "go back and look", "what did I do yesterday", "where did my day go", "timeline of my day", "how much time on", "how long did that actually take", "how much did I actually work", "active time", "time I spent".
 ---
 
@@ -202,3 +202,33 @@ See `references/recipes.md` for fuller multi-step workflows.
 ## When the modes return empty
 
 If a mode returns empty/unexpected output, run `--mode debug` first. It prints the entry-type distribution, content-block types, and probes for advisor + compact markers — useful when the transcript schema has drifted or when a session was truncated.
+---
+
+## Skill Feedback
+
+If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
+
+**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
+
+```bash
+gh issue create \
+  --repo ElliotDrel/e-stack \
+  --title "estack-read-claude-session-history: <concise summary>" \
+  --body "<description from user feedback — expected vs. actual behavior and context>"
+```
+
+**If `gh` is not installed**, build a pre-filled URL:
+
+```bash
+python3 -c "
+import urllib.parse
+title = 'estack-read-claude-session-history: <concise summary>'
+body = '<description from user feedback — expected vs. actual behavior and context>'
+base = 'https://github.com/ElliotDrel/e-stack/issues/new'
+print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
+"
+```
+
+Share the printed URL with the user and offer to open it in their browser.
+
+They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.

package/skills/estack-repo-search/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-repo-search
-version: 1.0.0
+version: 1.0.2
 description: >-
   (repo-search) Clone and search external GitHub repositories to answer questions about their
   code. Use this skill whenever the user references a repo you don't have local
@@ -78,7 +78,7 @@ gh issue create \
   --body "<description from user feedback — expected vs. actual behavior and context>"
 ```
 
-**If `gh` is not installed**, build a pre-filled URL and share it so the user can click, review, and submit:
+**If `gh` is not installed**, build a pre-filled URL:
 
 ```bash
 python3 -c "
@@ -90,4 +90,6 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
 "
 ```
 
-Share the printed URL with the user. They click it, review the pre-filled title and body, then click **Submit new issue**.
+Share the printed URL with the user and offer to open it in their browser.
+
+They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.