[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74B7HEAFXR570TGHG18PPRF":3,"skill-same:01M74B7HEAFXR570TGHG18PPRF":48},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":17,"linkOnly":18,"markdownContent":19,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":12,"repositoryHtmlUrl":25,"repositoryHomepageUrl":6,"ownerHtmlUrl":26,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":27,"install":28,"resources":41},"01M74B7HEAFXR570TGHG18PPRF","setup-agent-tail",null,"aicreator350\u002FaurionOFFICIELLE","aicreator350","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217751428?v=4","01M731QVHB22WCM6PDX5VFN1RV","01M731QVJ0TAD058M1SW9MY548",0,"MIT","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-agent-tail\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"﻿---name: setup-agent-taildescription: 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.---\u003Cobjective>Configure [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.\u003C\u002Fobjective>\u003Cquick_start>Run the auto-detect workflow below. The skill will:1. Detect project framework and structure2. Propose a configuration3. Install agent-tail after user confirms4. Configure framework plugins, CLI scripts, and gitignore\u003C\u002Fquick_start>\u003Cessential_principles>- Logs are written to `tmp\u002Flogs\u002Flatest\u002F` ÔÇö this is agent-tail's standard output directory- The `tmp\u002F` directory must be gitignored- Browser log capture requires a framework plugin (Vite or Next.js) in addition to the CLI- For monorepos, use `agent-tail-core init` at root and `agent-tail-core wrap` in each package- Always confirm the proposed configuration with the user before making changes\u003C\u002Fessential_principles>\u003Cprocess>**Step 1: Detect project type**Read these files to determine the project setup:- `package.json` ÔÇö check for framework dependencies (vite, next, react, etc.) and existing scripts- `vite.config.ts` \u002F `vite.config.js` ÔÇö Vite project indicator- `next.config.ts` \u002F `next.config.js` \u002F `next.config.mjs` ÔÇö Next.js project indicator- `turbo.json` \u002F `nx.json` \u002F `pnpm-workspace.yaml` \u002F `lerna.json` ÔÇö monorepo indicators- `.gitignore` ÔÇö check if `tmp\u002F` is already ignoredClassify the project as one of:- **vite** ÔÇö Vite-based project (React, Vue, Svelte, etc.)- **nextjs** ÔÇö Next.js project- **monorepo** ÔÇö Turborepo, Nx, pnpm workspaces, or Lerna- **node-cli** ÔÇö Plain Node.js \u002F any other project (CLI-only setup)**Step 2: Gather user preferences**Use AskUserQuestion to confirm detection and gather preferences:```Question 1: \"I detected a [framework] project. Is this correct?\"  - Yes, proceed  - No, it's actually [other options]Question 2: \"Which services should agent-tail manage?\"  - Based on detected scripts in package.json (e.g., \"dev\", \"api\", \"worker\")  - Let user add custom service names and commandsQuestion 3: \"Configure output destinations?\"  - Default (tmp\u002Flogs\u002Flatest\u002F) (Recommended)  - Custom directory  - Custom directory with combined.log disabledQuestion 4: \"Set up browser console log capture?\"  - Yes (Recommended) ÔÇö if Vite or Next.js detected  - No, server logs only  - [Skip this question for node-cli projects]```**Step 3: Install agent-tail**```bash# Detect package manager from lockfile# bun.lock ÔåÆ bun# pnpm-lock.yaml ÔåÆ pnpm# yarn.lock ÔåÆ yarn# package-lock.json ÔåÆ npm\u003Cpkg-manager> add -D agent-tail agent-tail-core```**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.**Step 4: Configure framework plugin**For each detected framework, apply the appropriate configuration. See references\u002Fframework-configs.md for exact code.- **Vite**: Add `agentTail()` plugin to vite.config- **Next.js**: Wrap config with `withAgentTail()`, add `AgentTailScript` to layout, create browser log API route- **Monorepo**: Add `agent-tail init` to root dev script, wrap each package with `agent-tail wrap`- **Node CLI**: No plugin needed, just CLI configuration**Step 5: Configure package.json scripts**Update `package.json` scripts to use agent-tail-core CLI. Transform existing dev scripts:```json{  \"scripts\": {    \"dev\": \"agent-tail-core run '\u003Cservice1>: \u003Coriginal-command>' '\u003Cservice2>: \u003Coriginal-command>'\"  }}```If user specified excludes or muting, add flags:```json{  \"scripts\": {    \"dev\": \"agent-tail-core run --exclude '[HMR]' --mute worker '\u003Cservices>'\"  }}```**Step 6: Update .gitignore**Add `tmp\u002F` to `.gitignore` if not already present.**Step 7: Verify setup**After configuration, tell the user:- Run their dev script to verify logs appear in `tmp\u002Flogs\u002Flatest\u002F`- Check that individual service logs and `combined.log` are created- If browser logging was enabled, verify console output appears in the browser log file\u003C\u002Fprocess>\u003Cconfiguration_options>These options can be presented to the user during setup:**Output directory**: Where logs are written (default: `tmp\u002Flogs\u002Flatest\u002F`)**Excludes**: Filter noisy log lines by substring or regex:- Common Vite excludes: `[HMR]`, `[vite]`, `Download the React DevTools`- Common Next.js excludes: `[Fast Refresh]`, `compiled successfully`**Service muting**: Hide specific services from terminal output while preserving log files:- Useful for noisy frontend dev servers when focused on backend work**Browser log capture**: Capture `console.*`, unhandled errors, and unhandled promise rejections from the browser**Log format**: All logs use timestamp + level + message format:`[10:30:00.123] [LOG    ] Message here`**Gitignore warning**: Agent-tail warns on startup if `tmp\u002F` is not gitignored. Disable with `warnOnMissingGitignore: false` in plugin options.\u003C\u002Fconfiguration_options>\u003Canti_patterns>\u003Cpitfall name=\"forgetting-browser-setup\">For Vite\u002FNext.js projects, the CLI alone does not capture browser console logs. The framework plugin is required for browser log capture.\u003C\u002Fpitfall>\u003Cpitfall name=\"monorepo-without-init\">In 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.\u003C\u002Fpitfall>\u003Cpitfall name=\"using-agent-tail-cli-instead-of-agent-tail-core\">The `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`.\u003C\u002Fpitfall>\u003Cpitfall name=\"overwriting-existing-scripts\">When modifying package.json scripts, preserve the original command inside the agent-tail runner. Do not replace the command, wrap it.\u003C\u002Fpitfall>\u003C\u002Fanti_patterns>\u003Csuccess_criteria>Setup is complete when:- agent-tail is installed as a dev dependency- Framework plugin configured (if Vite or Next.js)- package.json dev script wraps services with agent-tail- `tmp\u002F` is in .gitignore- User has been told how to verify the setup works\u003C\u002Fsuccess_criteria>\u003Creference_guides>**Framework-specific configuration code**: See references\u002Fframework-configs.md\u003C\u002Freference_guides>","---name: setup-agent-taildescription: 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.---\u003Cobjective>Configure [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.\u003C\u002Fobjective>\u003Cquick_start>Run the auto-detect workflow below. The skill will:1. Detect project framework and structure2. Propose a configuration3. Install agent-tail after user confirms4. Configure framework plugins, CLI scripts, and gitignore\u003C\u002Fquick_start>\u003Cessential_principles>- Logs are written to `tmp\u002Flogs\u002Flatest\u002F` ÔÇö this is agent-tail's standard output directory- The `tmp\u002F` directory must be gitignored- Browser log capture requires a framework plugin (Vite or Next.js) in addition to the CLI- For monorepos, use `agent-tail-core init` at root and `agent-tail-core wrap` in each package- Always confirm the proposed configuration with the user before making changes\u003C\u002Fessential_principles>\u003Cprocess>**Step 1: Detect project type**Read these files to determine the project setup:- `package.json` ÔÇö check for framework dependencies (vite, next, react, etc.) and existing scripts- `vite.config.ts` \u002F `vite.config.js` ÔÇö Vite project indicator- `next.config.ts` \u002F `next.config.js` \u002F `next.config.mjs` ÔÇö Next.js project indicator- `turbo.json` \u002F `nx.json` \u002F `pnpm-workspace.yaml` \u002F `lerna.json` ÔÇö monorepo indicators- `.gitignore` ÔÇö check if `tmp\u002F` is already ignoredClassify the project as one of:- **vite** ÔÇö Vite-based project (React, Vue, Svelte, etc.)- **nextjs** ÔÇö Next.js project- **monorepo** ÔÇö Turborepo, Nx, pnpm workspaces, or Lerna- **node-cli** ÔÇö Plain Node.js \u002F any other project (CLI-only setup)**Step 2: Gather user preferences**Use AskUserQuestion to confirm detection and gather preferences:```Question 1: \"I detected a [framework] project. Is this correct?\"  - Yes, proceed  - No, it's actually [other options]Question 2: \"Which services should agent-tail manage?\"  - Based on detected scripts in package.json (e.g., \"dev\", \"api\", \"worker\")  - Let user add custom service names and commandsQuestion 3: \"Configure output destinations?\"  - Default (tmp\u002Flogs\u002Flatest\u002F) (Recommended)  - Custom directory  - Custom directory with combined.log disabledQuestion 4: \"Set up browser console log capture?\"  - Yes (Recommended) ÔÇö if Vite or Next.js detected  - No, server logs only  - [Skip this question for node-cli projects]```**Step 3: Install agent-tail**```bash# Detect package manager from lockfile# bun.lock ÔåÆ bun# pnpm-lock.yaml ÔåÆ pnpm# yarn.lock ÔåÆ yarn# package-lock.json ÔåÆ npm\u003Cpkg-manager> add -D agent-tail agent-tail-core```**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.**Step 4: Configure framework plugin**For each detected framework, apply the appropriate configuration. See references\u002Fframework-configs.md for exact code.- **Vite**: Add `agentTail()` plugin to vite.config- **Next.js**: Wrap config with `withAgentTail()`, add `AgentTailScript` to layout, create browser log API route- **Monorepo**: Add `agent-tail init` to root dev script, wrap each package with `agent-tail wrap`- **Node CLI**: No plugin needed, just CLI configuration**Step 5: Configure package.json scripts**Update `package.json` scripts to use agent-tail-core CLI. Transform existing dev scripts:```json{  \"scripts\": {    \"dev\": \"agent-tail-core run '\u003Cservice1>: \u003Coriginal-command>' '\u003Cservice2>: \u003Coriginal-command>'\"  }}```If user specified excludes or muting, add flags:```json{  \"scripts\": {    \"dev\": \"agent-tail-core run --exclude '[HMR]' --mute worker '\u003Cservices>'\"  }}```**Step 6: Update .gitignore**Add `tmp\u002F` to `.gitignore` if not already present.**Step 7: Verify setup**After configuration, tell the user:- Run their dev script to verify logs appear in `tmp\u002Flogs\u002Flatest\u002F`- Check that individual service logs and `combined.log` are created- If browser logging was enabled, verify console output appears in the browser log file\u003C\u002Fprocess>\u003Cconfiguration_options>These options can be presented to the user during setup:**Output directory**: Where logs are written (default: `tmp\u002Flogs\u002Flatest\u002F`)**Excludes**: Filter noisy log lines by substring or regex:- Common Vite excludes: `[HMR]`, `[vite]`, `Download the React DevTools`- Common Next.js excludes: `[Fast Refresh]`, `compiled successfully`**Service muting**: Hide specific services from terminal output while preserving log files:- Useful for noisy frontend dev servers when focused on backend work**Browser log capture**: Capture `console.*`, unhandled errors, and unhandled promise rejections from the browser**Log format**: All logs use timestamp + level + message format:`[10:30:00.123] [LOG    ] Message here`**Gitignore warning**: Agent-tail warns on startup if `tmp\u002F` is not gitignored. Disable with `warnOnMissingGitignore: false` in plugin options.\u003C\u002Fconfiguration_options>\u003Canti_patterns>\u003Cpitfall name=\"forgetting-browser-setup\">For Vite\u002FNext.js projects, the CLI alone does not capture browser console logs. The framework plugin is required for browser log capture.\u003C\u002Fpitfall>\u003Cpitfall name=\"monorepo-without-init\">In 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.\u003C\u002Fpitfall>\u003Cpitfall name=\"using-agent-tail-cli-instead-of-agent-tail-core\">The `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`.\u003C\u002Fpitfall>\u003Cpitfall name=\"overwriting-existing-scripts\">When modifying package.json scripts, preserve the original command inside the agent-tail runner. Do not replace the command, wrap it.\u003C\u002Fpitfall>\u003C\u002Fanti_patterns>\u003Csuccess_criteria>Setup is complete when:- agent-tail is installed as a dev dependency- Framework plugin configured (if Vite or Next.js)- package.json dev script wraps services with agent-tail- `tmp\u002F` is in .gitignore- User has been told how to verify the setup works\u003C\u002Fsuccess_criteria>\u003Creference_guides>**Framework-specific configuration code**: See references\u002Fframework-configs.md\u003C\u002Freference_guides>",{},"main","5593cf3c72898ea9fc67225d452fe38f866ba6dd",".claude\u002Fskills\u002Fsetup-agent-tail","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE","https:\u002F\u002Fgithub.com\u002Faicreator350","2026-05-18 03:39:30",{"source":7,"skillName":5,"commands":29,"prompt":39,"zipAvailable":40},[30,33,36],{"tool":31,"command":32},"npx","npx skills add aicreator350\u002FaurionOFFICIELLE --skill setup-agent-tail",{"tool":34,"command":35},"bunx","bunx skills add aicreator350\u002FaurionOFFICIELLE --skill setup-agent-tail",{"tool":37,"command":38},"pnpm","pnpm dlx skills add aicreator350\u002FaurionOFFICIELLE --skill setup-agent-tail","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-agent-tail\u002FSKILL.md",true,[42],{"path":43,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":46,"sourceHtmlUrl":47},"references\u002Fframework-configs.md","REFERENCE","参考文档",4649,"https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-agent-tail\u002Freferences\u002Fframework-configs.md",[49,58,65,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":53,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":17},"01M74CAJWR9WB6DX1HF2V461Y0","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":17},"01M74CAFWC2H75GJ81B39C9RSW","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":17},"01M74CA9N2HTGCKJ93AE9NQMHA","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":17},"01M74CA364D4EVDXZZQRVK1Z73","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":17},"01M74C9YQZX1GVS18V0AYCYPZE","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":17},"01M74C9SEYD6F764Q1JACZX3A6","vercel-cli-with-tokens","Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[]]