[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYED0ZTH9FFCRHTZQ1VQJM":3,"skill-same:01M7AYED0ZTH9FFCRHTZQ1VQJM":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AYED0ZTH9FFCRHTZQ1VQJM","publish-personal-project",null,"Use when publishing a project to GitHub as a template.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdata-engineer\u002Fpublish-personal-project\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: publish-personal-project\ndescription: Use when publishing a project to GitHub as a template.\n---\n\n# Publish Personal Project as Open-Source Template\n\nTake a project built from personal material (vault notes, own profile, local keys) to a public repo a stranger can clone. The agent prepares and commits; **the user pushes\u002Fcreates the remote himself** — never run `git push` or `gh repo create` unless explicitly asked.\n\n## Design proposal first\n\nThis user's projects start from a design proposal note in `F:\\obsidian_note\\oralita_md\\personal\\ai\\` (published via the oat431\u002Foralita_md repo). The proposal carries the thesis, design decisions, architecture, and **roadmap**. The README links the public proposal URL and does NOT duplicate roadmap or design rationale.\n\n## README house conventions (user-corrected — apply without being asked)\n\n1. **\"How it works\" = Mermaid flowchart**, never ASCII art. Quote edge labels (`|\"label\"|`); show every designed exit path (error\u002Fqueue\u002Fskip branches), not just the happy path.\n2. **Quick start = numbered `### N. Step` sections, one code block per step** — each step is run → verify → move on. Never one giant combined block; the user explicitly rejected that as too compact.\n3. **Roadmap stays in the proposal**; README's Design section links it: `📄 [Full design proposal](url) — one-line summary of what it covers`.\n4. **License section**: `[MIT](LICENSE) © YEAR Full Name.` + any safety note (e.g. example data is fictional).\n5. Verify external URLs return 200 (`curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \u003Curl>`) before linking them in the README.\n\n## Personal-data separation pattern\n\nWhen the template is derived from the user's real data:\n\n- Live personal files (real profile, real resume, `.env`, run state, generated outputs) → **gitignored from day one**.\n- Ship `profile\u002F_template\u002F` (blank, annotated) + `profile\u002F_example\u002F` (a **fictional persona** filled to the depth you expect from users) instead of the real thing.\n- Ship `.env.example` with working provider options listed; never `.env`.\n- **Pre-commit audit is mandatory**: `git add -A`, then scan `git status --short` for personal names, keys, state files, and outputs (`grep -iE \"\u003Cusername>|\\.env$|state\u002F|targets\u002F\"`). Only commit after the staged list is clean. If files were already staged before gitignore rules existed, `git reset` and re-add — gitignore does not untrack staged files.\n- If the user commits via GitHub UI mid-session (e.g. Create LICENSE), re-check `git log` before local commits so history stays linear.\n\n## Tooling pitfalls (Windows\u002Fgit-bash + Bun + Hermes)\n\n- **Hermes secret redaction mangles file content** that contains literal API-key-assignment or grep-for-a-key patterns in scripts written via write_file — the redactor rewrites them and the script breaks silently. Workaround: compose the env-var name from string fragments inside the script (`name=\"LLM_\"\"API_\"\"KEY\"`, `val=\"${line#*=}\"`) and print only lengths, never values.\n- **Complex nested-quote one-liners fail through the terminal tool on git-bash** (`syntax error near unexpected token`). Write a `.sh` script with write_file and `bash script.sh` instead of inlining.\n- **Bun on Windows**: `Bun.spawn([...], {shell: true})` does not typecheck; use the Bun.$ template form (`.cwd(dir).quiet().nothrow()`) for shell commands like `npx ...`.\n- **Machine LLM keys** (for quick OpenAI-compatible API tests): the Hermes `.env` DashScope key is bound to an Anthropic-format endpoint and 401s against `\u002Fcompatible-mode`; the DeepSeek key works against `https:\u002F\u002Fapi.deepseek.com\u002Fv1`. Test with a 10-token PONG call before wiring a key into a project.\n- `bun run \u003Cscript>` propagates non-zero exit codes as `error: script exited with code N` — expected when a gate\u002Fcheck command fails by design; call the underlying `bun run engine\u002F...` directly when you need the raw code.\n\n## Verification before declaring done\n\nRun the real thing end-to-end and show actual output — for a loop\u002Fpipeline project that means: one full run producing the artifact, a second run proving dedup\u002Fidempotency (0 new work), and any built-in self-test (e.g. seed test that a guard catches injected bad data). Typecheck (`bun x tsc --noEmit --strict ...`) clean before commit.\n","# Publish Personal Project as Open-Source Template\n\nTake a project built from personal material (vault notes, own profile, local keys) to a public repo a stranger can clone. The agent prepares and commits; **the user pushes\u002Fcreates the remote himself** — never run `git push` or `gh repo create` unless explicitly asked.\n\n## Design proposal first\n\nThis user's projects start from a design proposal note in `F:\\obsidian_note\\oralita_md\\personal\\ai\\` (published via the oat431\u002Foralita_md repo). The proposal carries the thesis, design decisions, architecture, and **roadmap**. The README links the public proposal URL and does NOT duplicate roadmap or design rationale.\n\n## README house conventions (user-corrected — apply without being asked)\n\n1. **\"How it works\" = Mermaid flowchart**, never ASCII art. Quote edge labels (`|\"label\"|`); show every designed exit path (error\u002Fqueue\u002Fskip branches), not just the happy path.\n2. **Quick start = numbered `### N. Step` sections, one code block per step** — each step is run → verify → move on. Never one giant combined block; the user explicitly rejected that as too compact.\n3. **Roadmap stays in the proposal**; README's Design section links it: `📄 [Full design proposal](url) — one-line summary of what it covers`.\n4. **License section**: `[MIT](LICENSE) © YEAR Full Name.` + any safety note (e.g. example data is fictional).\n5. Verify external URLs return 200 (`curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \u003Curl>`) before linking them in the README.\n\n## Personal-data separation pattern\n\nWhen the template is derived from the user's real data:\n\n- Live personal files (real profile, real resume, `.env`, run state, generated outputs) → **gitignored from day one**.\n- Ship `profile\u002F_template\u002F` (blank, annotated) + `profile\u002F_example\u002F` (a **fictional persona** filled to the depth you expect from users) instead of the real thing.\n- Ship `.env.example` with working provider options listed; never `.env`.\n- **Pre-commit audit is mandatory**: `git add -A`, then scan `git status --short` for personal names, keys, state files, and outputs (`grep -iE \"\u003Cusername>|\\.env$|state\u002F|targets\u002F\"`). Only commit after the staged list is clean. If files were already staged before gitignore rules existed, `git reset` and re-add — gitignore does not untrack staged files.\n- If the user commits via GitHub UI mid-session (e.g. Create LICENSE), re-check `git log` before local commits so history stays linear.\n\n## Tooling pitfalls (Windows\u002Fgit-bash + Bun + Hermes)\n\n- **Hermes secret redaction mangles file content** that contains literal API-key-assignment or grep-for-a-key patterns in scripts written via write_file — the redactor rewrites them and the script breaks silently. Workaround: compose the env-var name from string fragments inside the script (`name=\"LLM_\"\"API_\"\"KEY\"`, `val=\"${line#*=}\"`) and print only lengths, never values.\n- **Complex nested-quote one-liners fail through the terminal tool on git-bash** (`syntax error near unexpected token`). Write a `.sh` script with write_file and `bash script.sh` instead of inlining.\n- **Bun on Windows**: `Bun.spawn([...], {shell: true})` does not typecheck; use the Bun.$ template form (`.cwd(dir).quiet().nothrow()`) for shell commands like `npx ...`.\n- **Machine LLM keys** (for quick OpenAI-compatible API tests): the Hermes `.env` DashScope key is bound to an Anthropic-format endpoint and 401s against `\u002Fcompatible-mode`; the DeepSeek key works against `https:\u002F\u002Fapi.deepseek.com\u002Fv1`. Test with a 10-token PONG call before wiring a key into a project.\n- `bun run \u003Cscript>` propagates non-zero exit codes as `error: script exited with code N` — expected when a gate\u002Fcheck command fails by design; call the underlying `bun run engine\u002F...` directly when you need the raw code.\n\n## Verification before declaring done\n\nRun the real thing end-to-end and show actual output — for a loop\u002Fpipeline project that means: one full run producing the artifact, a second run proving dedup\u002Fidempotency (0 new work), and any built-in self-test (e.g. seed test that a guard catches injected bad data). Typecheck (`bun x tsc --noEmit --strict ...`) clean before commit.\n",{"name":5,"description":7},"main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fdata-engineer\u002Fpublish-personal-project",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add oat431\u002Fhermes_config_backup --skill publish-personal-project",{"tool":39,"command":40},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill publish-personal-project",{"tool":42,"command":43},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill publish-personal-project","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdata-engineer\u002Fpublish-personal-project\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":52,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":52,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":52,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]