elliot-stack 1.0.25 → 1.0.28

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

@@ -1,6 +1,6 @@
 ---
 name: estack-customer-discovery
-version: 1.0.1
+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,100 +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
-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.1
+version: 1.0.3
 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
 ---
@@ -312,7 +312,7 @@ If the user doesn't have a SerpAPI key and asks for help getting one:
 2. Walk them to https://serpapi.com/users/sign_up — sign up with email.
 3. After signup, the API key is at https://serpapi.com/manage-api-key.
 4. To set it permanently, walk them through either:
-   - Saving it in their flight-planner config (`serpapi_key` field), or
+   - Saving it in their `~/.flight-planner/config.json` (`serpapi_key` field), or
    - Setting `SERPAPI_KEY` as an environment variable in their shell profile.
 5. If they don't want a key: confirm they want the WebSearch fallback. Set `serpapi_key: null` in config. Tell them: "I'll use WebSearch each run. Results won't be as complete and prices may be approximations."
 
@@ -334,105 +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:
-
-```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-flight-planner/scripts/fetch_flights.py

@@ -35,7 +35,7 @@ BASE_PARAMS = {
 
 
 def default_output_dir() -> Path:
-    base = Path(tempfile.gettempdir()) / "flight-planner"
+    base = Path(tempfile.gettempdir()) / "estack-flight-planner"
     base.mkdir(parents=True, exist_ok=True)
     return base
 

package/skills/estack-flight-planner/scripts/filter_flights.py

@@ -13,10 +13,10 @@ price distribution. The skill uses this to propose specific relaxations when
 hard filters return zero results.
 
 Usage:
-    python filter_flights.py --json-dir /tmp/flight-planner/ --max-price 200 --from IND --to EWR
-    python filter_flights.py --json-dir /tmp/flight-planner/ --max-price 200 \\
+    python filter_flights.py --json-dir /tmp/estack-flight-planner/ --max-price 200 --from IND --to EWR
+    python filter_flights.py --json-dir /tmp/estack-flight-planner/ --max-price 200 \\
         --soft-filters max-price,time-priority
-    python filter_flights.py --json-dir /tmp/flight-planner/ --cluster-analysis
+    python filter_flights.py --json-dir /tmp/estack-flight-planner/ --cluster-analysis
 
 All filter args (--max-price, --time-priority, --from, --to, --airlines, --nonstop)
 are required for normal filter mode (no defaults — caller passes config values).
@@ -192,7 +192,7 @@ def cluster_analysis(flights, max_price, bands, origins, dests, airlines, nonsto
 
 def main() -> int:
     p = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
-    default_dir = Path(tempfile.gettempdir()) / "flight-planner"
+    default_dir = Path(tempfile.gettempdir()) / "estack-flight-planner"
     p.add_argument("--json-dir", default=str(default_dir))
     p.add_argument("--max-price", type=int, default=None,
                    help="Max price in USD. Omit for no price filter.")

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

@@ -1,6 +1,6 @@
 ---
 name: estack-github-issue-tracker
-version: 1.0.1
+version: 1.0.3
 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,89 +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:
-
-```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-github-issue-tracker/bin/tracker-tools.cjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 
 /**
- * tracker-tools.cjs — Data service layer for github-issue-tracker skill.
+ * tracker-tools.cjs — Data service layer for estack-github-issue-tracker skill.
  *
  * Commands:
  *   startup --tracker <path>              Auth, parse tracker + config, create temp dir, discover issues

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

@@ -1,6 +1,6 @@
 ---
 name: estack-prompt-builder-coach
-version: 1.0.1
+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,7 +79,6 @@ 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

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

@@ -1,6 +1,6 @@
 ---
 name: estack-read-claude-session-history
-version: 1.0.1
+version: 1.0.3
 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".
 ---
 
@@ -13,7 +13,7 @@ Sessions are stored as `.jsonl` files. Reading them raw is hopeless: 1,000–5,0
 ## Quick start
 
 ```bash
-PY="C:\Users\2supe\.claude\skills\read-claude-session-history\scripts\read_transcript.py"
+PY="$HOME/.claude/skills/estack-read-claude-session-history/scripts/read_transcript.py"
 
 # What was the last thing the agent said in this session?
 python "$PY" --file <current-session.jsonl> --mode last
@@ -202,7 +202,6 @@ 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

package/skills/estack-read-claude-session-history/references/recipes.md

@@ -4,7 +4,7 @@ Multi-step workflows. For per-mode flag reference, see `modes.md`. For schema, s
 
 In all examples, `$PY` refers to:
 ```
-C:\Users\2supe\.claude\skills\read-claude-session-history\scripts\read_transcript.py
+~/.claude/skills/estack-read-claude-session-history/scripts/read_transcript.py
 ```
 
 ---

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

@@ -1,6 +1,6 @@
 ---
 name: estack-repo-search
-version: 1.0.1
+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,35 +78,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-repo-search: <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
-
-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-repo-search: <concise summary>" \
-  --body "<description from user feedback — expected vs. actual behavior and context>"
-```
-
 **If `gh` is not installed**, build a pre-filled URL:
 
 ```bash