[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7378AQG2RBXVMZ8XMXV57ND":3,"skill-same:01M7378AQG2RBXVMZ8XMXV57ND":48},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7378AQG2RBXVMZ8XMXV57ND","setup-agent-tail",null,"Configure agent-tail log aggregation for the current project. Auto-detects framework (Vite, Next.js, plain Node, monorepo) and sets up CLI runner, browser log plugins, and output destinations. Use when setting up agent-tail, configuring dev server logging, or piping logs for AI agent consumption.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-agent-tail\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: setup-agent-tail\ndescription: Configure agent-tail log aggregation for the current project. Auto-detects framework (Vite, Next.js, plain Node, monorepo) and sets up CLI runner, browser log plugins, and output destinations. Use when setting up agent-tail, configuring dev server logging, or piping logs for AI agent consumption.\n---\n\n\u003Cobjective>\nConfigure [agent-tail](https:\u002F\u002Fgithub.com\u002Fgillkyle\u002Fagent-tail) for the current project. Agent-tail pipes logs from dev servers and browser consoles into unified log files that AI coding agents can read and grep. This skill auto-detects the project type, proposes a configuration, and sets everything up after user confirmation.\n\u003C\u002Fobjective>\n\n\u003Cquick_start>\nRun the auto-detect workflow below. The skill will:\n\n1. Detect project framework and structure\n2. Propose a configuration\n3. Install agent-tail after user confirms\n4. Configure framework plugins, CLI scripts, and gitignore\n\u003C\u002Fquick_start>\n\n\u003Cessential_principles>\n- Logs are written to `tmp\u002Flogs\u002Flatest\u002F` — this is agent-tail's standard output directory\n- The `tmp\u002F` directory must be gitignored\n- Browser log capture requires a framework plugin (Vite or Next.js) in addition to the CLI\n- For monorepos, use `agent-tail-core init` at root and `agent-tail-core wrap` in each package\n- Always confirm the proposed configuration with the user before making changes\n\u003C\u002Fessential_principles>\n\n\u003Cprocess>\n**Step 1: Detect project type**\n\nRead these files to determine the project setup:\n\n- `package.json` — check for framework dependencies (vite, next, react, etc.) and existing scripts\n- `vite.config.ts` \u002F `vite.config.js` — Vite project indicator\n- `next.config.ts` \u002F `next.config.js` \u002F `next.config.mjs` — Next.js project indicator\n- `turbo.json` \u002F `nx.json` \u002F `pnpm-workspace.yaml` \u002F `lerna.json` — monorepo indicators\n- `.gitignore` — check if `tmp\u002F` is already ignored\n\nClassify the project as one of:\n- **vite** — Vite-based project (React, Vue, Svelte, etc.)\n- **nextjs** — Next.js project\n- **monorepo** — Turborepo, Nx, pnpm workspaces, or Lerna\n- **node-cli** — Plain Node.js \u002F any other project (CLI-only setup)\n\n**Step 2: Gather user preferences**\n\nUse AskUserQuestion to confirm detection and gather preferences:\n\n```\nQuestion 1: \"I detected a [framework] project. Is this correct?\"\n  - Yes, proceed\n  - No, it's actually [other options]\n\nQuestion 2: \"Which services should agent-tail manage?\"\n  - Based on detected scripts in package.json (e.g., \"dev\", \"api\", \"worker\")\n  - Let user add custom service names and commands\n\nQuestion 3: \"Configure output destinations?\"\n  - Default (tmp\u002Flogs\u002Flatest\u002F) (Recommended)\n  - Custom directory\n  - Custom directory with combined.log disabled\n\nQuestion 4: \"Set up browser console log capture?\"\n  - Yes (Recommended) — if Vite or Next.js detected\n  - No, server logs only\n  - [Skip this question for node-cli projects]\n```\n\n**Step 3: Install agent-tail**\n\n```bash\n# Detect package manager from lockfile\n# bun.lock → bun\n# pnpm-lock.yaml → pnpm\n# yarn.lock → yarn\n# package-lock.json → npm\n\n\u003Cpkg-manager> add -D agent-tail agent-tail-core\n```\n\n**Important**: The `agent-tail` umbrella package has a broken `bin` field that prevents the CLI from being linked. You must also install `agent-tail-core` explicitly — this is the package that provides the actual `agent-tail-core` CLI binary. Use `agent-tail-core` (not `agent-tail`) as the command name in all scripts.\n\n**Step 4: Configure framework plugin**\n\nFor each detected framework, apply the appropriate configuration. See references\u002Fframework-configs.md for exact code.\n\n- **Vite**: Add `agentTail()` plugin to vite.config\n- **Next.js**: Wrap config with `withAgentTail()`, add `AgentTailScript` to layout, create browser log API route\n- **Monorepo**: Add `agent-tail init` to root dev script, wrap each package with `agent-tail wrap`\n- **Node CLI**: No plugin needed, just CLI configuration\n\n**Step 5: Configure package.json scripts**\n\nUpdate `package.json` scripts to use agent-tail-core CLI. Transform existing dev scripts:\n\n```json\n{\n  \"scripts\": {\n    \"dev\": \"agent-tail-core run '\u003Cservice1>: \u003Coriginal-command>' '\u003Cservice2>: \u003Coriginal-command>'\"\n  }\n}\n```\n\nIf user specified excludes or muting, add flags:\n\n```json\n{\n  \"scripts\": {\n    \"dev\": \"agent-tail-core run --exclude '[HMR]' --mute worker '\u003Cservices>'\"\n  }\n}\n```\n\n**Step 6: Update .gitignore**\n\nAdd `tmp\u002F` to `.gitignore` if not already present.\n\n**Step 7: Verify setup**\n\nAfter configuration, tell the user:\n- Run their dev script to verify logs appear in `tmp\u002Flogs\u002Flatest\u002F`\n- Check that individual service logs and `combined.log` are created\n- If browser logging was enabled, verify console output appears in the browser log file\n\u003C\u002Fprocess>\n\n\u003Cconfiguration_options>\nThese options can be presented to the user during setup:\n\n**Output directory**: Where logs are written (default: `tmp\u002Flogs\u002Flatest\u002F`)\n\n**Excludes**: Filter noisy log lines by substring or regex:\n- Common Vite excludes: `[HMR]`, `[vite]`, `Download the React DevTools`\n- Common Next.js excludes: `[Fast Refresh]`, `compiled successfully`\n\n**Service muting**: Hide specific services from terminal output while preserving log files:\n- Useful for noisy frontend dev servers when focused on backend work\n\n**Browser log capture**: Capture `console.*`, unhandled errors, and unhandled promise rejections from the browser\n\n**Log format**: All logs use timestamp + level + message format:\n`[10:30:00.123] [LOG    ] Message here`\n\n**Gitignore warning**: Agent-tail warns on startup if `tmp\u002F` is not gitignored. Disable with `warnOnMissingGitignore: false` in plugin options.\n\u003C\u002Fconfiguration_options>\n\n\u003Canti_patterns>\n\u003Cpitfall name=\"forgetting-browser-setup\">\nFor Vite\u002FNext.js projects, the CLI alone does not capture browser console logs. The framework plugin is required for browser log capture.\n\u003C\u002Fpitfall>\n\n\u003Cpitfall name=\"monorepo-without-init\">\nIn monorepos using Turborepo\u002FNx, you must run `agent-tail-core init` before `turbo dev` (or equivalent). Without init, `agent-tail-core wrap` in child packages has no session to join.\n\u003C\u002Fpitfall>\n\n\u003Cpitfall name=\"using-agent-tail-cli-instead-of-agent-tail-core\">\nThe `agent-tail` umbrella package has a broken `bin` field — it references a nested path that package managers don't resolve correctly. Always use `agent-tail-core` as the CLI command in scripts, and always install `agent-tail-core` as an explicit devDependency alongside `agent-tail`.\n\u003C\u002Fpitfall>\n\n\u003Cpitfall name=\"overwriting-existing-scripts\">\nWhen modifying package.json scripts, preserve the original command inside the agent-tail runner. Do not replace the command, wrap it.\n\u003C\u002Fpitfall>\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\nSetup is complete when:\n- agent-tail is installed as a dev dependency\n- Framework plugin configured (if Vite or Next.js)\n- package.json dev script wraps services with agent-tail\n- `tmp\u002F` is in .gitignore\n- User has been told how to verify the setup works\n\u003C\u002Fsuccess_criteria>\n\n\u003Creference_guides>\n**Framework-specific configuration code**: See references\u002Fframework-configs.md\n\u003C\u002Freference_guides>\n","\u003Cobjective>\nConfigure [agent-tail](https:\u002F\u002Fgithub.com\u002Fgillkyle\u002Fagent-tail) for the current project. Agent-tail pipes logs from dev servers and browser consoles into unified log files that AI coding agents can read and grep. This skill auto-detects the project type, proposes a configuration, and sets everything up after user confirmation.\n\u003C\u002Fobjective>\n\n\u003Cquick_start>\nRun the auto-detect workflow below. The skill will:\n\n1. Detect project framework and structure\n2. Propose a configuration\n3. Install agent-tail after user confirms\n4. Configure framework plugins, CLI scripts, and gitignore\n\u003C\u002Fquick_start>\n\n\u003Cessential_principles>\n- Logs are written to `tmp\u002Flogs\u002Flatest\u002F` — this is agent-tail's standard output directory\n- The `tmp\u002F` directory must be gitignored\n- Browser log capture requires a framework plugin (Vite or Next.js) in addition to the CLI\n- For monorepos, use `agent-tail-core init` at root and `agent-tail-core wrap` in each package\n- Always confirm the proposed configuration with the user before making changes\n\u003C\u002Fessential_principles>\n\n\u003Cprocess>\n**Step 1: Detect project type**\n\nRead these files to determine the project setup:\n\n- `package.json` — check for framework dependencies (vite, next, react, etc.) and existing scripts\n- `vite.config.ts` \u002F `vite.config.js` — Vite project indicator\n- `next.config.ts` \u002F `next.config.js` \u002F `next.config.mjs` — Next.js project indicator\n- `turbo.json` \u002F `nx.json` \u002F `pnpm-workspace.yaml` \u002F `lerna.json` — monorepo indicators\n- `.gitignore` — check if `tmp\u002F` is already ignored\n\nClassify the project as one of:\n- **vite** — Vite-based project (React, Vue, Svelte, etc.)\n- **nextjs** — Next.js project\n- **monorepo** — Turborepo, Nx, pnpm workspaces, or Lerna\n- **node-cli** — Plain Node.js \u002F any other project (CLI-only setup)\n\n**Step 2: Gather user preferences**\n\nUse AskUserQuestion to confirm detection and gather preferences:\n\n```\nQuestion 1: \"I detected a [framework] project. Is this correct?\"\n  - Yes, proceed\n  - No, it's actually [other options]\n\nQuestion 2: \"Which services should agent-tail manage?\"\n  - Based on detected scripts in package.json (e.g., \"dev\", \"api\", \"worker\")\n  - Let user add custom service names and commands\n\nQuestion 3: \"Configure output destinations?\"\n  - Default (tmp\u002Flogs\u002Flatest\u002F) (Recommended)\n  - Custom directory\n  - Custom directory with combined.log disabled\n\nQuestion 4: \"Set up browser console log capture?\"\n  - Yes (Recommended) — if Vite or Next.js detected\n  - No, server logs only\n  - [Skip this question for node-cli projects]\n```\n\n**Step 3: Install agent-tail**\n\n```bash\n# Detect package manager from lockfile\n# bun.lock → bun\n# pnpm-lock.yaml → pnpm\n# yarn.lock → yarn\n# package-lock.json → npm\n\n\u003Cpkg-manager> add -D agent-tail agent-tail-core\n```\n\n**Important**: The `agent-tail` umbrella package has a broken `bin` field that prevents the CLI from being linked. You must also install `agent-tail-core` explicitly — this is the package that provides the actual `agent-tail-core` CLI binary. Use `agent-tail-core` (not `agent-tail`) as the command name in all scripts.\n\n**Step 4: Configure framework plugin**\n\nFor each detected framework, apply the appropriate configuration. See references\u002Fframework-configs.md for exact code.\n\n- **Vite**: Add `agentTail()` plugin to vite.config\n- **Next.js**: Wrap config with `withAgentTail()`, add `AgentTailScript` to layout, create browser log API route\n- **Monorepo**: Add `agent-tail init` to root dev script, wrap each package with `agent-tail wrap`\n- **Node CLI**: No plugin needed, just CLI configuration\n\n**Step 5: Configure package.json scripts**\n\nUpdate `package.json` scripts to use agent-tail-core CLI. Transform existing dev scripts:\n\n```json\n{\n  \"scripts\": {\n    \"dev\": \"agent-tail-core run '\u003Cservice1>: \u003Coriginal-command>' '\u003Cservice2>: \u003Coriginal-command>'\"\n  }\n}\n```\n\nIf user specified excludes or muting, add flags:\n\n```json\n{\n  \"scripts\": {\n    \"dev\": \"agent-tail-core run --exclude '[HMR]' --mute worker '\u003Cservices>'\"\n  }\n}\n```\n\n**Step 6: Update .gitignore**\n\nAdd `tmp\u002F` to `.gitignore` if not already present.\n\n**Step 7: Verify setup**\n\nAfter configuration, tell the user:\n- Run their dev script to verify logs appear in `tmp\u002Flogs\u002Flatest\u002F`\n- Check that individual service logs and `combined.log` are created\n- If browser logging was enabled, verify console output appears in the browser log file\n\u003C\u002Fprocess>\n\n\u003Cconfiguration_options>\nThese options can be presented to the user during setup:\n\n**Output directory**: Where logs are written (default: `tmp\u002Flogs\u002Flatest\u002F`)\n\n**Excludes**: Filter noisy log lines by substring or regex:\n- Common Vite excludes: `[HMR]`, `[vite]`, `Download the React DevTools`\n- Common Next.js excludes: `[Fast Refresh]`, `compiled successfully`\n\n**Service muting**: Hide specific services from terminal output while preserving log files:\n- Useful for noisy frontend dev servers when focused on backend work\n\n**Browser log capture**: Capture `console.*`, unhandled errors, and unhandled promise rejections from the browser\n\n**Log format**: All logs use timestamp + level + message format:\n`[10:30:00.123] [LOG    ] Message here`\n\n**Gitignore warning**: Agent-tail warns on startup if `tmp\u002F` is not gitignored. Disable with `warnOnMissingGitignore: false` in plugin options.\n\u003C\u002Fconfiguration_options>\n\n\u003Canti_patterns>\n\u003Cpitfall name=\"forgetting-browser-setup\">\nFor Vite\u002FNext.js projects, the CLI alone does not capture browser console logs. The framework plugin is required for browser log capture.\n\u003C\u002Fpitfall>\n\n\u003Cpitfall name=\"monorepo-without-init\">\nIn monorepos using Turborepo\u002FNx, you must run `agent-tail-core init` before `turbo dev` (or equivalent). Without init, `agent-tail-core wrap` in child packages has no session to join.\n\u003C\u002Fpitfall>\n\n\u003Cpitfall name=\"using-agent-tail-cli-instead-of-agent-tail-core\">\nThe `agent-tail` umbrella package has a broken `bin` field — it references a nested path that package managers don't resolve correctly. Always use `agent-tail-core` as the CLI command in scripts, and always install `agent-tail-core` as an explicit devDependency alongside `agent-tail`.\n\u003C\u002Fpitfall>\n\n\u003Cpitfall name=\"overwriting-existing-scripts\">\nWhen modifying package.json scripts, preserve the original command inside the agent-tail runner. Do not replace the command, wrap it.\n\u003C\u002Fpitfall>\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\nSetup is complete when:\n- agent-tail is installed as a dev dependency\n- Framework plugin configured (if Vite or Next.js)\n- package.json dev script wraps services with agent-tail\n- `tmp\u002F` is in .gitignore\n- User has been told how to verify the setup works\n\u003C\u002Fsuccess_criteria>\n\n\u003Creference_guides>\n**Framework-specific configuration code**: See references\u002Fframework-configs.md\n\u003C\u002Freference_guides>\n",{"name":5,"description":7},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fsetup-agent-tail",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill setup-agent-tail",{"tool":40,"command":41},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill setup-agent-tail",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill setup-agent-tail","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-agent-tail\u002FSKILL.md",true,[],[49,57,64,72,80,88],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]