From 1e0e094bca99046227822bec50424adba2abf77d Mon Sep 17 00:00:00 2001 From: teahubxyz Date: Wed, 14 Oct 2026 21:49:24 +0000 Subject: [PATCH] skills README: point to SKILLS.md (#7) Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01H4upF5LVwmPDDqrhdUfnXh --- .agents/skills/README.md | 37 ++++--------------------------------- 1 file changed, 4 insertions(+), 33 deletions(-) diff --git a/.agents/skills/README.md b/.agents/skills/README.md index 5e0cc9b..47c13ff 100644 --- a/.agents/skills/README.md +++ b/.agents/skills/README.md @@ -1,34 +1,5 @@ -# Skills (`.agents/skills/`) +# `.agents/skills/` -Vendored agent skills, Agent Skills spec (one folder per skill, `SKILL.md` + `references/`). - -**Who sees this folder.** Codex, Copilot/VS Code, Gemini CLI and most open-source harnesses (OpenCode, goose, Pi, -OpenHands) read `.agents/skills/` natively. **Claude Code does not**: it reads `.claude/skills/` only (it does follow -symlinked skill folders there). Until per-skill symlinks exist under `.claude/skills/`, and for every scheduled loop -regardless of harness, name the skill by path in the prompt: "read `.agents/skills//SKILL.md` and follow it". -Explicit pointers trigger far more reliably than description matching, so loops should do this anyway, and should -load only the one to three skills the task needs. - -| Skill | What | Upstream | -|---|---|---| -| `brag-slim` | One-file launch-video skill: project dir or URL → ~20s `brag.mp4` + poster + share copy | latent-spaces/brag (MIT) | -| `product-marketing` | Foundation: product, audience, positioning. Every other marketing skill reads this first | coreyhaines31/marketingskills (MIT) | -| `launch` | Launch planning, shipped-changes posts, site-launch QA | " | -| `social` | Platform playbooks (incl. Bluesky), post templates, listening, short-form video | " | -| `content-strategy` | Content plans and distribution | " | -| `copywriting` | Marketing copy, frameworks, AI-tell removal | " | -| `marketing-loops` | Recurring self-running marketing loops (catalog, guardrails, state) — the piece Time can schedule | " | - -Starter subset, 2026-10-14. The full marketingskills set is ~50 skills; add more by copying the folder from upstream -(`evals/` folders left out on purpose). Update by re-vendoring; note the upstream version in the commit message. - -Known caveats: -- `brag-slim` was built for Claude Opus 5.5; upstream sends other models to the full `/brag` workflow. Use it on Claude seats. -- `copywriting` hands email and popup copy to sibling skills (`emails`, `popups`) that are not vendored here. -- `social/references/listening.md` pulls untrusted public text (Reddit, HN, Bluesky, YouTube). Run listening in a seat - with no secrets, and let it write a digest rather than edit shared files. -- Upstream's AGENTS.md tells agents to fetch `VERSIONS.md` from GitHub at runtime. That file is deliberately not - vendored; updates come in as reviewed diffs, never by an agent fetching at run time. - -First use: run `product-marketing` once per product and save its output as the product's marketing context, so the -other skills have something to read. Change that file only by pull request. +The vendored skill folders. The contract — which skills to load for which task, where each came from, and how far +it is trusted — is in [`/SKILLS.md`](../../SKILLS.md). Don't edit these files in place: changes arrive by PR, as +SKILLS.md describes.