opencode-skills-collection 3.1.14 → 3.1.16

package/bundled-skills/instagram/scripts/export.py

@@ -17,6 +17,19 @@ import sys
 from datetime import datetime, timezone
 from pathlib import Path
 
+
+def safe_user_path(path_value, base_dir="."):
+    """Resolve a CLI path under the current workspace."""
+    if base_dir != ".":
+        raise ValueError("Custom base directories are not supported for CLI paths")
+    base_path = Path.cwd().resolve()
+    resolved_path = Path(path_value).expanduser().resolve()
+    try:
+        resolved_path.relative_to(base_path)
+    except ValueError as exc:
+        raise ValueError(f"Path escapes allowed directory: {path_value}") from exc
+    return resolved_path
+
 sys.path.insert(0, str(Path(__file__).parent))
 
 _db = None
@@ -55,11 +68,9 @@ def export_json(records: list, output_dir: Path, name: str) -> Path:
     output_dir.mkdir(parents=True, exist_ok=True)
     ts = datetime.now(timezone.utc).strftime("%Y%m%d_%H%M%S")
     path = output_dir / f"instagram_{name}_{ts}.json"
-    with open(path, "w", encoding="utf-8") as f:
-        json.dump(
-            {"exported_at": datetime.now(timezone.utc).isoformat(), "total": len(records), "data": records},
-            f, ensure_ascii=False, indent=2,
-        )
+    payload = {"exported_at": datetime.now(timezone.utc).isoformat(), "total": len(records), "data": records}
+    with safe_user_path(path).open("w", encoding="utf-8") as f:
+        f.write(json.dumps(payload, ensure_ascii=False, indent=2))
     print(f"[JSON] {len(records)} registros ->{path}")
     return path
 
@@ -68,7 +79,7 @@ def export_jsonl(records: list, output_dir: Path, name: str) -> Path:
     output_dir.mkdir(parents=True, exist_ok=True)
     ts = datetime.now(timezone.utc).strftime("%Y%m%d_%H%M%S")
     path = output_dir / f"instagram_{name}_{ts}.jsonl"
-    with open(path, "w", encoding="utf-8") as f:
+    with safe_user_path(path).open("w", encoding="utf-8") as f:
         for rec in records:
             f.write(json.dumps(rec, ensure_ascii=False) + "\n")
     print(f"[JSONL] {len(records)} registros ->{path}")
@@ -82,7 +93,7 @@ def export_csv_file(records: list, output_dir: Path, name: str) -> Path:
     output_dir.mkdir(parents=True, exist_ok=True)
     ts = datetime.now(timezone.utc).strftime("%Y%m%d_%H%M%S")
     path = output_dir / f"instagram_{name}_{ts}.csv"
-    with open(path, "w", newline="", encoding="utf-8-sig") as f:
+    with safe_user_path(path).open("w", newline="", encoding="utf-8-sig") as f:
         writer = csv.DictWriter(f, fieldnames=list(records[0].keys()), extrasaction="ignore")
         writer.writeheader()
         writer.writerows(records)

package/bundled-skills/interview-style-doc-building/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: interview-style-doc-building
+description: "Build structured strategy documents by asking one question at a time and patching the file."
+category: productivity
+risk: critical
+source: community
+source_repo: davidondrej/skills
+source_type: community
+date_added: "2026-07-07"
+author: davidondrej
+tags: [documentation, interview, planning]
+tools: [claude, codex]
+license: "MIT"
+license_source: "https://github.com/davidondrej/skills/blob/main/LICENSE"
+---
+
+# Interview-Style Doc Building
+
+The user's preferred mode for creating durable strategic docs. AI does NOT propose content — AI asks one question, the user answers, AI patches the file, AI asks the next question. The file IS the conversation's output, updated incrementally.
+
+## When to Use
+
+- Building a new SSOT file (life priorities, life vision, principles, frameworks, ranked lists).
+- Filling out a structured doc the user explicitly wants to author themselves.
+- Quarterly/annual reviews where the user's words go into the file.
+
+**NOT for:** day planning (use `day-plan`), task triage (`organize-tasks`), or anything where AI proposes content first.
+
+## The Loop
+
+1. **Create the file** with a skeleton (header, sections, "to be filled in" placeholders). Single `write_file` for the new file. After this, NEVER overwrite — only `patch`.
+2. **Ask ONE question.** Concise. Specific. Single-faceted. Open-ended where possible.
+3. **Wait for the answer.** Don't ask the next question yet.
+4. **Patch the file** with the user's answer in the correct section.
+5. **Re-ask** — next question, or follow-up if the answer was incomplete.
+6. Repeat until the file is complete.
+
+## Hard Rules
+
+- **One question at a time.** Never dump multiple questions in a single message. The user has flagged this.
+- **Patch, don't overwrite.** After the initial skeleton, use `patch` for every update. Never `write_file` to an existing doc.
+- **Update the file BEFORE asking the next question.** Order: receive answer → patch file → ask next question. Not the reverse.
+- **Lists from the user are UNORDERED SETS.** When the user lists items in response to "which X should we cover?" or "what are the Ys?", that is a SET, not a ranking. Never infer rank, priority, or sequence from the order they typed them. If you need ordering, ask explicitly: "Which of these is #1?"
+- **Ask dynamics, not names.** When the user references a person, don't ask "who is X?" — ask about the role/dynamic.
+- **No snark, no attitude, no filler.** Concise questions, concise acknowledgments.
+- **No speculative additions.** Don't invent sections, edge cases, or "anything else?" prompts unless the user asks.
+
+## Question Design
+
+- **Domain-discovery, not confirmation.** "What wins against everything else?" — not "Is Business #1?"
+- **Surface new reality.** Each question should pull out info AI doesn't already have.
+- **Engine-move framing where applicable.** "What's the thing that, if true, makes the rest obvious?"
+- **Concrete over abstract.** "What's #2 — the domain that wins against everything except #1?" beats "Tell me about your second priority."
+
+## File Patching Pattern
+
+After each answer:
+1. Read the relevant section (if not already in context).
+2. `patch` with `old_string` = placeholder or previous entry, `new_string` = updated content with the user's words preserved.
+3. Confirm the diff. Move on.
+
+For ranked lists, append one rank at a time:
+```
+1. **Business** — Q2 #1 goal: ...
+2. **Health** — get below 81.0 kg, sleep 9h/day, ...
+```
+Each rank gets patched in as the user confirms it.
+
+## Common Pitfalls
+
+- **Assuming order from a set.** The user lists "A, B, C, D" → AI writes "1. A, 2. B, 3. C, 4. D" → the user flags it. ALWAYS confirm rank explicitly.
+- **Asking too many questions at once.** Even bundling 2 violates the rule.
+- **Overwriting the file** instead of patching specific sections — destroys prior content.
+- **Adding AI-generated content** to fill out sections. Sections stay empty until the user provides the content.
+- **Skipping the file update** between Q&A pairs — the doc falls out of sync.
+
+## Pairing with Other Skills
+
+- `day-plan` — different pattern (task triage), not interview-style.
+- `organize-tasks` — Todoist-specific.
+- `memory-management` — separate from this; persona/preferences go to memory.
+
+## Limitations
+
+- Adapted from `davidondrej/skills`; verify local paths, tools, credentials, and agent features before acting.
+- For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.

package/bundled-skills/junta-leiloeiros/scripts/export.py

@@ -18,6 +18,19 @@ import json
 import sys
 from datetime import datetime, timezone
 from pathlib import Path
+
+
+def safe_user_path(path_value, base_dir="."):
+    """Resolve a CLI path under the current workspace."""
+    if base_dir != ".":
+        raise ValueError("Custom base directories are not supported for CLI paths")
+    base_path = Path.cwd().resolve()
+    resolved_path = Path(path_value).expanduser().resolve()
+    try:
+        resolved_path.relative_to(base_path)
+    except ValueError as exc:
+        raise ValueError(f"Path escapes allowed directory: {path_value}") from exc
+    return resolved_path
 from typing import List, Optional
 
 sys.path.insert(0, str(Path(__file__).parent))
@@ -31,13 +44,9 @@ def export_json(records: list, output_dir: Path, suffix: str = "") -> Path:
     output_dir.mkdir(parents=True, exist_ok=True)
     ts = datetime.now(timezone.utc).strftime("%Y%m%d_%H%M%S")
     path = output_dir / f"leiloeiros{suffix}_{ts}.json"
-    with open(path, "w", encoding="utf-8") as f:
-        json.dump(
-            {"exported_at": datetime.now(timezone.utc).isoformat(), "total": len(records), "data": records},
-            f,
-            ensure_ascii=False,
-            indent=2,
-        )
+    payload = {"exported_at": datetime.now(timezone.utc).isoformat(), "total": len(records), "data": records}
+    with safe_user_path(path).open("w", encoding="utf-8") as f:
+        f.write(json.dumps(payload, ensure_ascii=False, indent=2))
     print(f"[JSON] {len(records)} registros → {path}")
     return path
 
@@ -46,7 +55,7 @@ def export_jsonl(records: list, output_dir: Path, suffix: str = "") -> Path:
     output_dir.mkdir(parents=True, exist_ok=True)
     ts = datetime.now(timezone.utc).strftime("%Y%m%d_%H%M%S")
     path = output_dir / f"leiloeiros{suffix}_{ts}.jsonl"
-    with open(path, "w", encoding="utf-8") as f:
+    with safe_user_path(path).open("w", encoding="utf-8") as f:
         for rec in records:
             f.write(json.dumps(rec, ensure_ascii=False) + "\n")
     print(f"[JSONL] {len(records)} registros → {path}")
@@ -62,7 +71,7 @@ def export_csv(records: list, output_dir: Path, suffix: str = "") -> Path:
     ts = datetime.now(timezone.utc).strftime("%Y%m%d_%H%M%S")
     path = output_dir / f"leiloeiros{suffix}_{ts}.csv"
 
-    with open(path, "w", newline="", encoding="utf-8-sig") as f:
+    with safe_user_path(path).open("w", newline="", encoding="utf-8-sig") as f:
         writer = csv.DictWriter(f, fieldnames=list(records[0].keys()), extrasaction="ignore")
         writer.writeheader()
         writer.writerows(records)
@@ -106,7 +115,7 @@ def main():
     db = Database()
     db.init()
 
-    output_dir = Path(args.output)
+    output_dir = safe_user_path(args.output)
     estados = [e.upper() for e in args.estado] if args.estado else None
 
     if estados:

package/bundled-skills/landing-page-generator/scripts/landing_page_scaffolder.py

@@ -16,6 +16,20 @@ import sys
 from typing import Dict, List, Any, Optional
 from datetime import datetime
 import html as html_module
+from pathlib import Path
+
+
+def safe_user_path(path_value, base_dir="."):
+    """Resolve a CLI path under the current workspace."""
+    if base_dir != ".":
+        raise ValueError("Custom base directories are not supported for CLI paths")
+    base_path = Path.cwd().resolve()
+    resolved_path = Path(path_value).expanduser().resolve()
+    try:
+        resolved_path.relative_to(base_path)
+    except ValueError as exc:
+        raise ValueError(f"Path escapes allowed directory: {path_value}") from exc
+    return resolved_path
 
 
 def escape(text: str) -> str:
@@ -557,7 +571,7 @@ def main():
         output = generate_html(config)
 
     if args.output:
-        with open(args.output, "w") as f:
+        with safe_user_path(args.output).open("w") as f:
             f.write(output)
         print(f"Landing page written to {args.output}")
     else:

package/bundled-skills/linear-claude-skill/SKILL.md

@@ -127,10 +127,12 @@ If setup reports a missing API key:
 
 ```bash
 # Option A: Add to shell profile (~/.zshrc or ~/.bashrc)
-export LINEAR_API_KEY="lin_api_your_key_here"
+read -rsp "Linear API key: " LINEAR_API_KEY
+echo
+export LINEAR_API_KEY
 
 # Option B: Add to Claude Code environment
-echo 'LINEAR_API_KEY=lin_api_your_key_here' >> ~/.claude/.env
+printf 'LINEAR_API_KEY=%s\n' "$LINEAR_API_KEY" >> ~/.claude/.env
 
 # Then reload your shell or restart Claude Code
 ```

package/bundled-skills/linkedin-post-writer/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: linkedin-post-writer
+description: "Draft LinkedIn posts from 16 tested hook formulas mapped to engagement goals (comments, reposts, likes, saves), with 2026 algorithm formatting rules and an AI-tell scrub pass before publishing."
+category: marketing
+risk: none
+source: community
+source_repo: sergebulaev/linkedin-skills
+source_type: community
+date_added: "2026-07-06"
+author: sergebulaev
+tags: [linkedin, copywriting, hooks, social-media, personal-brand, content-marketing]
+tools: [claude, codex, cursor, gemini]
+license: "MIT"
+license_source: "https://github.com/sergebulaev/linkedin-skills/blob/main/LICENSE"
+---
+
+# LinkedIn Post Writer
+
+## Overview
+
+Drafts long-form LinkedIn posts using 16 hook formulas that were reverse-engineered from posts that outperformed their authors' baselines in 2025-2026, each with a reference engagement number. Instead of asking "what should I write", the workflow asks "what should this post earn" (comments, reposts, likes, or saves), shortlists 2-3 matching formulas, fills the chosen skeleton with the user's voice, then scrubs the draft for AI tells before it ships.
+
+This is the flagship skill from [sergebulaev/linkedin-skills](https://github.com/sergebulaev/linkedin-skills), a 10-skill LinkedIn bundle (writer, humanizer, pre-publish audit, comment drafter, reply handler, hook extractor, content planner, profile optimizer, engager analytics, thread monitor) installable as a Claude Code or Codex plugin. This standalone version covers the drafting workflow; scheduling and publishing automation live in the full bundle.
+
+## When to Use This Skill
+
+- Use when the user says "write me a LinkedIn post about X"
+- Use when the user has a topic and a rough angle but needs a hook and structure
+- Use when the user wants to pick from proven post formats instead of improvising
+- Use when a draft exists but the hook is weak and needs a formula-based rebuild
+- Not for replying to comments or optimizing profiles; this skill only drafts posts
+
+## How It Works
+
+### Step 1: Gather inputs
+
+Collect: topic, angle, target audience (founders, operators, marketers), desired length (short 300-500, medium 900-1,300, or long 1,500-1,900 characters), and any raw material the user already has (numbers, anecdotes, names).
+
+### Step 2: Pick the formula by engagement goal first
+
+Ask (or infer) what the post should earn, then shortlist:
+
+| Goal | Earned by | Formulas |
+|---|---|---|
+| Comments | questions, contrarian takes, vulnerability | F4 Time-Anchor Confession, F10 Contrarian + Receipts, F12 Permission Slip, F9 Curiosity-Gap |
+| Reposts | quotable maxims, tributes, "X isn't Y" distinctions | F14 Named Gratitude, F2 R.I.P. Obituary, F8 Paid-vs-Free Reversal |
+| Likes | emotional stories, celebrations, status-strip | F11 Emotional Cold-Open, F13 Bait-and-Switch Reversal, F16 Status-Strip Humility |
+| Saves | simplifications, exact how-to, frameworks | F15 Explain-to-Kids, F7 Odd-Precision Money Ledger, F8 Paid-vs-Free Reversal |
+
+The full set of 16, with reference engagement:
+
+| Code | Formula | Reference | Best for |
+|---|---|---|---|
+| F1 | Platform Risk Anaphora | 4,240 eng | Category and platform-risk arguments |
+| F2 | R.I.P. Obituary | 3,822 eng | Era-ending claims, industry pivots |
+| F3 | Year-over-Year Pivot | 494 eng, 3.74x baseline | Identity shifts, founder reflection |
+| F4 | Time-Anchor Confession | 1,519+ eng | Vulnerability, voice reset |
+| F5 | Self-Proving Meta | 1,082 eng, 435 comments | Commitments and tests in public |
+| F6 | Comment-Gate Lead Magnet | 717-3,008 eng | List building (max once a month) |
+| F7 | Odd-Precision Money Ledger | 1,755 eng, 9.4x baseline | Build logs, cost breakdowns |
+| F8 | Paid-vs-Free Reversal | 550 eng, 19.64x baseline | Framework giveaways |
+| F9 | Curiosity-Gap Teaser | 306 eng, 4.25x baseline | Surprise and behind-the-scenes stories |
+| F10 | Contrarian + Historical Receipts | 3,083 eng | Sacred-cow takes backed by history |
+| F11 | Emotional Cold-Open | high raw reach | Real stories with emotional stakes |
+| F12 | Permission Slip | comment-heavy | Encouragement to a discouraged audience |
+| F13 | Bait-and-Switch Reversal | high raw reach | Bad-news framing that turns into an upgrade |
+| F14 | Named Gratitude / Tribute | repost-heavy | Thanking mentors, teams, departing colleagues |
+| F15 | Explain-to-Kids | save-heavy | Demystifying jargon into a reference post |
+| F16 | Status-Strip Humility | like-heavy | Senior voices trading prestige for warmth |
+
+Important caveat: F1-F10 references are engagement counts or format multipliers against the author's own baseline; F11-F16 references are raw corpus reach, often inflated by a famous author or a reshare. The two groups measure different things, so never rank formulas across groups by number.
+
+The full skeletons for all 16 formulas are bundled with this skill in [references/hook-formulas.md](references/hook-formulas.md), along with per-formula warnings and the "Never do" list.
+
+### Step 3: Draft the post
+
+Read the chosen formula's skeleton from the bundled [references/hook-formulas.md](references/hook-formulas.md) and fill it with the user's voice and material, respecting the 2026 formatting rules:
+
+- Hook lands in the first 210 characters (before the "... see more" fold)
+- 900-1,300 characters is the sweet spot for text posts
+- Double line-breaks between ideas, never walls of text
+- 0-2 hashtags, placed at the end
+- No external links in the body (put links in the first comment)
+- Prefer "How I" over "How to": first-person experience hooks outperform generic instruction 2-3x
+- Put one specific number in the first sentence ($873.47 beats $900; 40,000 beats "a lot")
+
+### Step 4: Scrub AI tells
+
+Before showing the draft: strip em dashes, AI vocabulary ("game-changer", "deep dive", "delve"), rule-of-three lists without receipts, and generic openers like "In today's fast-paced world". Add human fingerprints: at least one specific number, one named entity, and one first-person concrete detail per 100 words. Vary sentence length aggressively (mix 3-word and 25-word sentences).
+
+### Step 5: Present the result
+
+Show the user: formula used, full draft, character count, and a suggested posting window (Tuesday to Thursday, 7:30-9:00 AM local time performs best for B2B audiences).
+
+## Examples
+
+### Example 1: Founder build-log (F7 Odd-Precision Money Ledger)
+
+```text
+User:  write a post about what my bootstrapped SaaS actually costs to run
+Agent: Goal check: this reads like a saves play (people screenshot cost
+       breakdowns). Best fit is F7 Odd-Precision Money Ledger (9.4x baseline).
+       Draft hook:
+
+       "My SaaS costs $412.83 a month to run. Here is every line item."
+
+       Then the ledger: hosting $94.20, email $35.00, monitoring $18.63...
+       exact numbers only, totals that actually add up, one lesson at the end.
+```
+
+### Example 2: Goal-first selection
+
+```text
+User:  I want a post that gets real comments, topic: why I stopped doing demos
+Agent: Comment-earners are F4 Confession, F10 Contrarian, F12 Permission Slip.
+       For "I stopped doing X" the strongest is F10 Contrarian + Receipts:
+       open with the unpopular claim, back it with 2 historical parallels,
+       close with a question that forces side-picking. Reference: 3,083 eng.
+```
+
+## Best Practices
+
+- ✅ Pick the formula by engagement goal first, topic second
+- ✅ Lead with a real failure or a specific number in the first 3 lines
+- ✅ Include one moment of genuine vulnerability or concrete stakes; pure insight posts underperform in 2026
+- ❌ Don't blend two hook formulas in one post; it dilutes both
+- ❌ Don't use F5 Self-Proving Meta unless the user will actually keep the promise
+- ❌ Don't pair F7 Money Ledger with rounded or invented numbers; readers notice
+- ❌ Don't open with an all-caps line ("THIS CHANGED EVERYTHING")
+- ❌ Don't frame LinkedIn as inferior inside a LinkedIn post
+
+## Limitations
+
+- Reference engagement numbers describe the 2025-2026 corpus the formulas were extracted from; they are priors, not guarantees, and LinkedIn's ranking changes over time.
+- The skill drafts text posts; it does not generate images, carousels, or video scripts.
+- This standalone version does not schedule or publish. Scheduling, comment drafting, reply handling, and engagement analytics require the full bundle from the source repo.
+- Voice quality depends on the raw material the user provides; a formula cannot invent authentic anecdotes, and the skill should ask for real details rather than fabricate them.
+
+## Common Pitfalls
+
+- **Problem:** The draft sounds like every other AI-written LinkedIn post.
+  **Solution:** Run Step 4 ruthlessly. Cut em dashes, cut "game-changer" vocabulary, and force one concrete first-person detail per 100 words.
+- **Problem:** The hook is buried in paragraph two.
+  **Solution:** The first 210 characters must carry the hook; everything before the fold decides the expand rate.
+- **Problem:** Comparing F11's raw reach to F8's 19.64x multiplier and picking F11 "because the number is bigger".
+  **Solution:** The columns measure different things. Match formula to goal and topic, not to the largest number.
+- **Problem:** Post gets reach but zero comments.
+  **Solution:** The formula was picked for the wrong goal. Comment-earners end with a question or a side-picking claim, not a summary.
+
+## Related Skills
+
+- `@linkedin-content-generator` - broader LinkedIn content suite (carousels, newsletters, calendars)
+- `@linkedin-profile-optimizer` - profile and authority optimization rather than post drafting
+- `@social-post-writer-seo` - multi-platform social copy when LinkedIn is not the only target
+
+## Additional Resources
+
+- [Source repo with all 16 formula skeletons and worked examples](https://github.com/sergebulaev/linkedin-skills)
+- [Full 10-skill bundle install (Claude Code / Codex plugin)](https://github.com/sergebulaev/linkedin-skills#install)