[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YCKPP4AK5X2JS112NHW0X":3,"skill-same:01M72YCKPP4AK5X2JS112NHW0X":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72YCKPP4AK5X2JS112NHW0X","logtape",null,"Use this skill when writing any code that uses LogTape for logging in JavaScript or TypeScript.  Covers getting loggers, the structured message syntax, configuration, library author rules, context, lazy evaluation, testing, and common mistakes to avoid.  Trigger whenever the user is adding logging to a project, debugging log output, or integrating LogTape with a framework.","marcioaltoe\u002Fskills","marcioaltoe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1562865?v=4","01M72Y3750J2CG00P0H2AHDRSZ","Marcio Altoé","01M72Y37642F46H36R4E4S7BNA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F05-implementation-loop\u002Flogtape\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: logtape\ndescription: >\n  Use this skill when writing any code that uses LogTape for logging in\n  JavaScript or TypeScript.  Covers getting loggers, the structured message\n  syntax, configuration, library author rules, context, lazy evaluation,\n  testing, and common mistakes to avoid.  Trigger whenever the user is\n  adding logging to a project, debugging log output, or integrating LogTape\n  with a framework.\nlicense: MIT\n---\n\nLogTape skill for AI coding assistants\n======================================\n\nLogTape is a zero-dependency, library-first logging framework for JavaScript\nand TypeScript that works across Deno, Node.js, Bun, browsers, and edge\nfunctions.\n\nFull documentation: \u003Chttps:\u002F\u002Flogtape.org\u002F>\n\n\nGetting a logger\n----------------\n\nAlways use `getLogger()` with an **array** category to enable hierarchical\nfiltering.  The hierarchy works like a path: a parent category's configuration\napplies to all children.\n\n~~~~ typescript\nimport { getLogger } from \"@logtape\u002Flogtape\";\n\n\u002F\u002F Good: array form enables hierarchical filtering\nconst logger = getLogger([\"my-app\", \"users\", \"auth\"]);\n\n\u002F\u002F Acceptable shorthand for a single-segment category\nconst rootLogger = getLogger(\"my-app\");\n~~~~\n\nChoose category segments that reflect your module structure so that operators\ncan selectively enable\u002Fdisable logging per subsystem.\n\nUse `logger.getChild(\"sub\")` to derive a child logger without repeating the\nfull category:\n\n~~~~ typescript\nconst dbLogger = logger.getChild(\"database\");\n\u002F\u002F category = [\"my-app\", \"users\", \"auth\", \"database\"]\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fcategories.md> for details.\n\n\nStructured messages\n-------------------\n\nUse **named placeholders** with a properties object.  This keeps messages\nparseable and properties searchable:\n\n~~~~ typescript\n\u002F\u002F Correct: structured message with named placeholders\nlogger.info(\"User {userId} logged in from {ip}\", { userId, ip });\n\n\u002F\u002F Correct: structured data without a message\nlogger.info({ userId, ip, action: \"login\" });\n\n\u002F\u002F Nested property access (since 1.2.0)\nlogger.info(\"Name: {user.name}\", { user: { name: \"Alice\" } });\n~~~~\n\nTemplate literal syntax is available for quick debug logging but does **not**\nproduce structured data:\n\n~~~~ typescript\n\u002F\u002F Template literal: convenient but not structured\nlogger.debug`User ${userId} logged in`;\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fstruct.md> for full structured logging details.\n\n\nSeverity levels\n---------------\n\nLogTape provides six levels, from most to least verbose:\n\n| Level     | Use for                                               |\n| --------- | ----------------------------------------------------- |\n| `trace`   | Very fine-grained diagnostic output                   |\n| `debug`   | Developer-facing diagnostic messages                  |\n| `info`    | Normal operational events (startup, shutdown, etc.)   |\n| `warning` | Unexpected but recoverable situations                 |\n| `error`   | Errors that affect a single operation                 |\n| `fatal`   | Unrecoverable errors that require process termination |\n\nUse the lowest appropriate level.  Reserve `error`\u002F`fatal` for actual failures;\navoid using them for expected conditions like validation errors.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Flevels.md> for details.\n\n\nConfiguration\n-------------\n\n### Async configuration (most common)\n\n`configure()` is **application-only**.  It must be `await`ed and called\n**exactly once** at startup (e.g., in your entry point):\n\n~~~~ typescript\nimport { configure, getConsoleSink } from \"@logtape\u002Flogtape\";\n\nawait configure({\n  sinks: {\n    console: getConsoleSink(),\n  },\n  loggers: [\n    {\n      category: \"my-app\",\n      lowestLevel: \"debug\",\n      sinks: [\"console\"],\n    },\n  ],\n});\n~~~~\n\n### Synchronous configuration\n\nUse `configureSync()` when you cannot use `await` (e.g., top-level in CommonJS,\nor in a synchronous startup path):\n\n~~~~ typescript\nimport { configureSync, getConsoleSink } from \"@logtape\u002Flogtape\";\n\nconfigureSync({\n  sinks: {\n    console: getConsoleSink(),\n  },\n  loggers: [\n    {\n      category: \"my-app\",\n      lowestLevel: \"debug\",\n      sinks: [\"console\"],\n    },\n  ],\n});\n~~~~\n\n> **Limitation:** `configureSync()` cannot use `AsyncDisposable` sinks such as\n> `getStreamSink()` or sinks created with `fromAsyncSink()`.\n\n### Key rules\n\n -  `configure()` returns a `Promise`; always `await` it.\n -  `configureSync()` returns `void`; do not `await` it.\n -  Call either one **once**.  Calling again without resetting first throws\n    `ConfigError`.\n -  Do **not** mix async and sync: if you used `configure()`, reset with\n    `await reset()`; if you used `configureSync()`, reset with `resetSync()`.\n -  For tests, call `await reset()` (or `resetSync()`) in teardown.\n\n### Framework-specific patterns\n\n -  **React**: configure **before** `createRoot()`.\n -  **Vue**: configure **before** `app.mount()`.\n -  **Next.js**: use *instrumentation.js* (server) or\n    *instrumentation-client.js* (client).\n -  **SvelteKit**: configure in *hooks.server.ts*.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fconfig.md> for all options.\n\n\nLibrary author rule\n-------------------\n\n**Never call `configure()` or `configureSync()` in library code.**  Libraries\nshould only call `getLogger()` and log messages.  The application that depends\non your library decides how (or whether) to configure sinks and levels.\n\n~~~~ typescript\n\u002F\u002F my-lib\u002Fsrc\u002Fclient.ts — library code\nimport { getLogger } from \"@logtape\u002Flogtape\";\n\n\u002F\u002F Good: just get a logger, don't configure\nconst logger = getLogger([\"my-lib\", \"client\"]);\n\nexport function fetchData(url: string) {\n  logger.debug(\"Fetching {url}\", { url });\n  \u002F\u002F ...\n}\n~~~~\n\nIf your library wraps other LogTape-using libraries, use `withCategoryPrefix()`\nto nest their logs under your category:\n\n~~~~ typescript\nimport { withCategoryPrefix } from \"@logtape\u002Flogtape\";\n\nexport function myOperation() {\n  return withCategoryPrefix([\"my-lib\"], () => {\n    \u002F\u002F Logs from inner libraries appear as [\"my-lib\", ...their-category]\n    innerLib.doWork();\n  });\n}\n~~~~\n\n> **Note:** `withCategoryPrefix()` requires `contextLocalStorage` to be\n> configured by the application.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Flibrary.md> for the full guide.\n\n\nContext with `with()` and lazy evaluation\n-----------------------------------------\n\n### Adding explicit context\n\nUse `logger.with()` to create a child logger that attaches properties to every\nsubsequent log call:\n\n~~~~ typescript\nconst reqLogger = logger.with({ requestId, userId });\nreqLogger.info(\"Processing order {orderId}\", { orderId });\n\u002F\u002F Log record will contain requestId, userId, AND orderId\n~~~~\n\n### Implicit context (request tracing)\n\nUse `withContext()` to propagate context across an entire call stack without\nthreading loggers manually.  Requires `contextLocalStorage` in configuration:\n\n~~~~ typescript\nimport { configure, getConsoleSink, withContext } from \"@logtape\u002Flogtape\";\nimport { AsyncLocalStorage } from \"node:async_hooks\";\n\nawait configure({\n  sinks: { console: getConsoleSink() },\n  loggers: [{ category: \"app\", sinks: [\"console\"] }],\n  contextLocalStorage: new AsyncLocalStorage(),\n});\n\nfunction handleRequest(req: Request) {\n  withContext({ requestId: crypto.randomUUID() }, () => {\n    \u002F\u002F All logs inside this callback automatically include requestId\n    processRequest(req);\n  });\n}\n~~~~\n\n> **Note:** Implicit contexts are not available in browsers yet.\n\n### Lazy evaluation\n\nWrap expensive computations with `lazy()` so they only run when the level is\nenabled:\n\n~~~~ typescript\nimport { getLogger, lazy } from \"@logtape\u002Flogtape\";\n\nconst logger = getLogger([\"my-app\"]);\nlogger.debug(\"System state: {state}\", {\n  state: lazy(() => JSON.stringify(getExpensiveState())),\n});\n~~~~\n\nFor structured data, pass a callback as the second argument:\n\n~~~~ typescript\nlogger.debug(\"Diagnostics\", () => ({\n  heap: process.memoryUsage().heapUsed,\n  uptime: process.uptime(),\n}));\n~~~~\n\nFor **async** lazy evaluation, pass an async callback and `await` the result:\n\n~~~~ typescript\nawait logger.info(\"User details\", async () => ({\n  user: await fetchUserDetails(),\n}));\n~~~~\n\nFor multiple expensive log calls, use `isEnabledFor()`:\n\n~~~~ typescript\nif (logger.isEnabledFor(\"debug\")) {\n  const snapshot = await captureExpensiveSnapshot();\n  logger.debug(\"Snapshot: {data}\", { data: snapshot });\n}\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Flazy.md> and\n\u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fcontexts.md> for details.\n\n\nLogging errors\n--------------\n\nPass `Error` objects directly to `error()` or `fatal()`.  You can attach\nextra properties as a second argument:\n\n~~~~ typescript\ntry {\n  await riskyOperation();\n} catch (error) {\n  logger.error(error, { operation: \"riskyOperation\", userId });\n}\n~~~~\n\n\nSinks and formatters\n--------------------\n\n### Built-in sinks\n\n~~~~ typescript\nimport {\n  configure,\n  getConsoleSink,\n  getStreamSink,\n} from \"@logtape\u002Flogtape\";\n\nawait configure({\n  sinks: {\n    console: getConsoleSink(),\n    stderr: getStreamSink(Writable.toWeb(process.stderr)),\n  },\n  loggers: [{ category: \"app\", sinks: [\"console\"] }],\n});\n~~~~\n\n### Sink filters\n\nUse `withFilter()` to route different levels to different sinks:\n\n~~~~ typescript\nimport { configure, getConsoleSink, withFilter } from \"@logtape\u002Flogtape\";\n\nawait configure({\n  sinks: {\n    errorsOnly: withFilter(getConsoleSink(), \"error\"),\n    allLevels: getConsoleSink(),\n  },\n  loggers: [\n    { category: \"app\", sinks: [\"allLevels\", \"errorsOnly\"] },\n  ],\n});\n~~~~\n\n### Formatters\n\n~~~~ typescript\nimport {\n  configure,\n  getAnsiColorFormatter,\n  getConsoleSink,\n  getJsonLinesFormatter,\n  getLogfmtFormatter,\n} from \"@logtape\u002Flogtape\";\n\n\u002F\u002F Pretty ANSI-colored output for development\ngetConsoleSink({ formatter: getAnsiColorFormatter() });\n\n\u002F\u002F JSON Lines for production \u002F log aggregation\ngetConsoleSink({ formatter: getJsonLinesFormatter() });\n\n\u002F\u002F logfmt for readable structured logs\ngetConsoleSink({ formatter: getLogfmtFormatter() });\n~~~~\n\nFor even nicer development output, use `@logtape\u002Fpretty`:\n\n~~~~ typescript\nimport { getPrettyFormatter } from \"@logtape\u002Fpretty\";\n\ngetConsoleSink({ formatter: getPrettyFormatter() });\n~~~~\n\n### Disposal\n\nNon-blocking sinks and stream sinks hold resources.  In **edge functions** or\nshort-lived processes, explicitly dispose before exit:\n\n~~~~ typescript\nimport { dispose } from \"@logtape\u002Flogtape\";\n\n\u002F\u002F At shutdown\nawait dispose();\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fsinks.md> and\n\u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fformatters.md> for details.\n\n\nData redaction\n--------------\n\nUse `@logtape\u002Fredaction` to prevent sensitive data from reaching log output.\n\n### Pattern-based redaction (scans formatted text)\n\nWrap a formatter with `redactByPattern()` to catch data like emails, credit\ncard numbers, or JWTs anywhere in the log output:\n\n~~~~ typescript\nimport { defaultConsoleFormatter, getConsoleSink } from \"@logtape\u002Flogtape\";\nimport {\n  EMAIL_ADDRESS_PATTERN,\n  JWT_PATTERN,\n  redactByPattern,\n} from \"@logtape\u002Fredaction\";\n\nconst sink = getConsoleSink({\n  formatter: redactByPattern(defaultConsoleFormatter, [\n    EMAIL_ADDRESS_PATTERN,\n    JWT_PATTERN,\n  ]),\n});\n~~~~\n\nBuilt-in patterns: `EMAIL_ADDRESS_PATTERN`, `CREDIT_CARD_NUMBER_PATTERN`,\n`JWT_PATTERN`, `US_SSN_PATTERN`, `KR_RRN_PATTERN`.\n\n### Field-based redaction (removes\u002Freplaces properties by name)\n\nWrap a sink with `redactByField()` to strip sensitive fields from structured\nlog data before it reaches the sink:\n\n~~~~ typescript\nimport { getConsoleSink } from \"@logtape\u002Flogtape\";\nimport { redactByField } from \"@logtape\u002Fredaction\";\n\n\u002F\u002F Uses DEFAULT_REDACT_FIELDS (password, secret, token, etc.)\nconst sink = redactByField(getConsoleSink());\n\n\u002F\u002F Or customize with replacement instead of removal\nconst sink2 = redactByField(getConsoleSink(), {\n  fieldPatterns: [\u002Fpassword\u002Fi, \u002Fsecret\u002Fi, \u002Fapi[-_]?key\u002Fi],\n  action: () => \"[REDACTED]\",\n});\n~~~~\n\n### Combining both for maximum security\n\n~~~~ typescript\nconst sink = redactByField(\n  getConsoleSink({\n    formatter: redactByPattern(defaultConsoleFormatter, [\n      EMAIL_ADDRESS_PATTERN,\n      JWT_PATTERN,\n    ]),\n  }),\n);\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fredaction.md> for details.\n\n\nAdaptors for existing loggers\n-----------------------------\n\nIf the project already uses winston, Pino, or log4js, use an adaptor instead\nof `configure()`:\n\n~~~~ typescript\nimport { install } from \"@logtape\u002Fadaptor-winston\";\nimport winston from \"winston\";\n\nconst winstonLogger = winston.createLogger({ \u002F* ... *\u002F });\ninstall(winstonLogger);\n\u002F\u002F All LogTape logs now route through winston\n~~~~\n\nAvailable: `@logtape\u002Fadaptor-winston`, `@logtape\u002Fadaptor-pino`,\n`@logtape\u002Fadaptor-log4js`.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fadaptors.md> for details.\n\n\nTesting\n-------\n\nFor tests, use `@logtape\u002Ftesting` and assert on collected records:\n\n~~~~ typescript\nimport { configure, getLogger, reset } from \"@logtape\u002Flogtape\";\nimport { createLogRecorder } from \"@logtape\u002Ftesting\";\n\nconst recorder = createLogRecorder();\n\ntry {\n  await configure({\n    sinks: { recorder: recorder.sink },\n    loggers: [\n      { category: \"test\", sinks: [\"recorder\"] },\n      { category: [\"logtape\", \"meta\"], sinks: [] },\n    ],\n  });\n\n  const logger = getLogger([\"test\"]);\n  logger.info(\"User {userId} logged in.\", { userId: \"u-123\" });\n\n  recorder.assertLogged({\n    category: \"test\",\n    level: \"info\",\n    message: \u002F^User .+ logged in\\.$\u002F,\n    properties: { userId: \"u-123\" },\n  });\n} finally {\n  await reset();\n}\n~~~~\n\nIf using `configureSync()`, reset with `resetSync()`:\n\n~~~~ typescript\nimport { configureSync, resetSync } from \"@logtape\u002Flogtape\";\n\nconfigureSync({ \u002F* ... *\u002F });\n\u002F\u002F ... test ...\nresetSync();\n~~~~\n\nAlways call `reset()` \u002F `resetSync()` in test teardown so that each test can\nconfigure independently.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Ftesting.md> for more patterns.\n\n\nAvailable packages\n------------------\n\n### Sink packages\n\n| Package                     | Description            |\n| --------------------------- | ---------------------- |\n| `@logtape\u002Ffile`             | File and rotating file |\n| `@logtape\u002Fotel`             | OpenTelemetry          |\n| `@logtape\u002Fsentry`           | Sentry                 |\n| `@logtape\u002Fsyslog`           | Syslog                 |\n| `@logtape\u002Fcloudwatch-logs`  | AWS CloudWatch Logs    |\n| `@logtape\u002Fwindows-eventlog` | Windows Event Log      |\n\n### Framework integrations\n\n| Package                 | Description               |\n| ----------------------- | ------------------------- |\n| `@logtape\u002Fdrizzle-orm`  | Drizzle ORM query logging |\n| `@logtape\u002Felysia`       | Elysia HTTP logging       |\n| `@logtape\u002Fexpress`      | Express HTTP logging      |\n| `@logtape\u002Ffastify`      | Fastify HTTP logging      |\n| `@logtape\u002Fgraphql-yoga` | GraphQL Yoga logging      |\n| `@logtape\u002Fhono`         | Hono HTTP logging         |\n| `@logtape\u002Fkoa`          | Koa HTTP logging          |\n\n### Formatters\n\n| Package              | Description              |\n| -------------------- | ------------------------ |\n| `@logtape\u002Fpretty`    | Pretty console formatter |\n| `@logtape\u002Fredaction` | Sensitive data redaction |\n\n### Testing\n\n| Package            | Description                  |\n| ------------------ | ---------------------------- |\n| `@logtape\u002Ftesting` | Log recording and assertions |\n\n### Adaptors (for existing loggers)\n\n| Package                    | Description           |\n| -------------------------- | --------------------- |\n| `@logtape\u002Fadaptor-pino`    | Pino compatibility    |\n| `@logtape\u002Fadaptor-winston` | Winston compatibility |\n| `@logtape\u002Fadaptor-log4js`  | log4js compatibility  |\n\n\nCommon mistakes\n---------------\n\n### Using template literals for structured data\n\n~~~~ typescript\n\u002F\u002F WRONG: template literals don't produce structured data\nlogger.info`User ${userId} performed ${action}`;\n\n\u002F\u002F CORRECT: use placeholders for structured, searchable logs\nlogger.info(\"User {userId} performed {action}\", { userId, action });\n~~~~\n\n### String concatenation\n\n~~~~ typescript\n\u002F\u002F WRONG: loses structure, always evaluates\nlogger.info(\"User \" + userId + \" logged in from \" + ip);\n\n\u002F\u002F CORRECT\nlogger.info(\"User {userId} logged in from {ip}\", { userId, ip });\n~~~~\n\n### Calling `configure()` in library code\n\n~~~~ typescript\n\u002F\u002F WRONG: library must never configure LogTape\nimport { configure } from \"@logtape\u002Flogtape\";\nawait configure({ \u002F* ... *\u002F });  \u002F\u002F Don't do this in a library!\n\n\u002F\u002F CORRECT: just use getLogger()\nimport { getLogger } from \"@logtape\u002Flogtape\";\nconst logger = getLogger([\"my-lib\"]);\n~~~~\n\n### Forgetting to `await configure()`\n\n~~~~ typescript\n\u002F\u002F WRONG: configure() returns a Promise; without await, logging may\n\u002F\u002F not work when you expect it to\nconfigure({ \u002F* ... *\u002F });\n\n\u002F\u002F CORRECT\nawait configure({ \u002F* ... *\u002F });\n\n\u002F\u002F Or use the synchronous variant if you can't await\nconfigureSync({ \u002F* ... *\u002F });\n~~~~\n\n### Mixing async\u002Fsync configure and reset\n\n~~~~ typescript\n\u002F\u002F WRONG: mismatched pair causes errors\nawait configure({ \u002F* ... *\u002F });\nresetSync();  \u002F\u002F Can't sync-reset an async config!\n\n\u002F\u002F CORRECT: match configure and reset variants\nawait configure({ \u002F* ... *\u002F });\nawait reset();\n\n\u002F\u002F Or:\nconfigureSync({ \u002F* ... *\u002F });\nresetSync();\n~~~~\n\n### Using `console.log` alongside LogTape\n\n~~~~ typescript\n\u002F\u002F WRONG: bypasses LogTape's filtering, formatting, and routing\nconsole.log(\"User logged in:\", userId);\n\n\u002F\u002F CORRECT: use the logger so the message goes through configured sinks\nlogger.info(\"User {userId} logged in\", { userId });\n~~~~\n\n### Flat categories\n\n~~~~ typescript\n\u002F\u002F WRONG: single flat string prevents granular filtering\nconst logger = getLogger(\"myapp\");\n\n\u002F\u002F CORRECT: hierarchical array enables per-module control\nconst logger = getLogger([\"myapp\", \"auth\", \"oauth\"]);\n~~~~\n\n### Logging sensitive data without redaction\n\n~~~~ typescript\n\u002F\u002F WRONG: password ends up in log files\nlogger.info(\"Login attempt for {email} with {password}\", { email, password });\n\n\u002F\u002F CORRECT: never log secrets; use @logtape\u002Fredaction if needed\nlogger.info(\"Login attempt for {email}\", { email });\n~~~~\n\n\nBest practices summary\n----------------------\n\n -  One `configure()` or `configureSync()` call at startup\n -  Always `await configure()`; never `await configureSync()`\n -  Match reset variant to configure variant\n -  Hierarchical array categories (e.g., `[\"app\", \"module\", \"sub\"]`)\n -  Structured messages with named placeholders, not string interpolation\n -  `lazy()` or callback for expensive computations\n -  `logger.with()` for request-scoped context\n -  `withContext()` + `AsyncLocalStorage` for implicit context propagation\n -  `error`\u002F`fatal` only for real failures\n -  Libraries: never configure, just `getLogger()`\n -  Tests: `reset()` \u002F `resetSync()` in teardown, buffer sink for assertions\n -  Never log sensitive data (passwords, tokens, PII)\n -  Use `dispose()` \u002F `disposeSync()` in edge functions or short-lived\n    processes\n","LogTape skill for AI coding assistants\n======================================\n\nLogTape is a zero-dependency, library-first logging framework for JavaScript\nand TypeScript that works across Deno, Node.js, Bun, browsers, and edge\nfunctions.\n\nFull documentation: \u003Chttps:\u002F\u002Flogtape.org\u002F>\n\n\nGetting a logger\n----------------\n\nAlways use `getLogger()` with an **array** category to enable hierarchical\nfiltering.  The hierarchy works like a path: a parent category's configuration\napplies to all children.\n\n~~~~ typescript\nimport { getLogger } from \"@logtape\u002Flogtape\";\n\n\u002F\u002F Good: array form enables hierarchical filtering\nconst logger = getLogger([\"my-app\", \"users\", \"auth\"]);\n\n\u002F\u002F Acceptable shorthand for a single-segment category\nconst rootLogger = getLogger(\"my-app\");\n~~~~\n\nChoose category segments that reflect your module structure so that operators\ncan selectively enable\u002Fdisable logging per subsystem.\n\nUse `logger.getChild(\"sub\")` to derive a child logger without repeating the\nfull category:\n\n~~~~ typescript\nconst dbLogger = logger.getChild(\"database\");\n\u002F\u002F category = [\"my-app\", \"users\", \"auth\", \"database\"]\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fcategories.md> for details.\n\n\nStructured messages\n-------------------\n\nUse **named placeholders** with a properties object.  This keeps messages\nparseable and properties searchable:\n\n~~~~ typescript\n\u002F\u002F Correct: structured message with named placeholders\nlogger.info(\"User {userId} logged in from {ip}\", { userId, ip });\n\n\u002F\u002F Correct: structured data without a message\nlogger.info({ userId, ip, action: \"login\" });\n\n\u002F\u002F Nested property access (since 1.2.0)\nlogger.info(\"Name: {user.name}\", { user: { name: \"Alice\" } });\n~~~~\n\nTemplate literal syntax is available for quick debug logging but does **not**\nproduce structured data:\n\n~~~~ typescript\n\u002F\u002F Template literal: convenient but not structured\nlogger.debug`User ${userId} logged in`;\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fstruct.md> for full structured logging details.\n\n\nSeverity levels\n---------------\n\nLogTape provides six levels, from most to least verbose:\n\n| Level     | Use for                                               |\n| --------- | ----------------------------------------------------- |\n| `trace`   | Very fine-grained diagnostic output                   |\n| `debug`   | Developer-facing diagnostic messages                  |\n| `info`    | Normal operational events (startup, shutdown, etc.)   |\n| `warning` | Unexpected but recoverable situations                 |\n| `error`   | Errors that affect a single operation                 |\n| `fatal`   | Unrecoverable errors that require process termination |\n\nUse the lowest appropriate level.  Reserve `error`\u002F`fatal` for actual failures;\navoid using them for expected conditions like validation errors.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Flevels.md> for details.\n\n\nConfiguration\n-------------\n\n### Async configuration (most common)\n\n`configure()` is **application-only**.  It must be `await`ed and called\n**exactly once** at startup (e.g., in your entry point):\n\n~~~~ typescript\nimport { configure, getConsoleSink } from \"@logtape\u002Flogtape\";\n\nawait configure({\n  sinks: {\n    console: getConsoleSink(),\n  },\n  loggers: [\n    {\n      category: \"my-app\",\n      lowestLevel: \"debug\",\n      sinks: [\"console\"],\n    },\n  ],\n});\n~~~~\n\n### Synchronous configuration\n\nUse `configureSync()` when you cannot use `await` (e.g., top-level in CommonJS,\nor in a synchronous startup path):\n\n~~~~ typescript\nimport { configureSync, getConsoleSink } from \"@logtape\u002Flogtape\";\n\nconfigureSync({\n  sinks: {\n    console: getConsoleSink(),\n  },\n  loggers: [\n    {\n      category: \"my-app\",\n      lowestLevel: \"debug\",\n      sinks: [\"console\"],\n    },\n  ],\n});\n~~~~\n\n> **Limitation:** `configureSync()` cannot use `AsyncDisposable` sinks such as\n> `getStreamSink()` or sinks created with `fromAsyncSink()`.\n\n### Key rules\n\n -  `configure()` returns a `Promise`; always `await` it.\n -  `configureSync()` returns `void`; do not `await` it.\n -  Call either one **once**.  Calling again without resetting first throws\n    `ConfigError`.\n -  Do **not** mix async and sync: if you used `configure()`, reset with\n    `await reset()`; if you used `configureSync()`, reset with `resetSync()`.\n -  For tests, call `await reset()` (or `resetSync()`) in teardown.\n\n### Framework-specific patterns\n\n -  **React**: configure **before** `createRoot()`.\n -  **Vue**: configure **before** `app.mount()`.\n -  **Next.js**: use *instrumentation.js* (server) or\n    *instrumentation-client.js* (client).\n -  **SvelteKit**: configure in *hooks.server.ts*.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fconfig.md> for all options.\n\n\nLibrary author rule\n-------------------\n\n**Never call `configure()` or `configureSync()` in library code.**  Libraries\nshould only call `getLogger()` and log messages.  The application that depends\non your library decides how (or whether) to configure sinks and levels.\n\n~~~~ typescript\n\u002F\u002F my-lib\u002Fsrc\u002Fclient.ts — library code\nimport { getLogger } from \"@logtape\u002Flogtape\";\n\n\u002F\u002F Good: just get a logger, don't configure\nconst logger = getLogger([\"my-lib\", \"client\"]);\n\nexport function fetchData(url: string) {\n  logger.debug(\"Fetching {url}\", { url });\n  \u002F\u002F ...\n}\n~~~~\n\nIf your library wraps other LogTape-using libraries, use `withCategoryPrefix()`\nto nest their logs under your category:\n\n~~~~ typescript\nimport { withCategoryPrefix } from \"@logtape\u002Flogtape\";\n\nexport function myOperation() {\n  return withCategoryPrefix([\"my-lib\"], () => {\n    \u002F\u002F Logs from inner libraries appear as [\"my-lib\", ...their-category]\n    innerLib.doWork();\n  });\n}\n~~~~\n\n> **Note:** `withCategoryPrefix()` requires `contextLocalStorage` to be\n> configured by the application.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Flibrary.md> for the full guide.\n\n\nContext with `with()` and lazy evaluation\n-----------------------------------------\n\n### Adding explicit context\n\nUse `logger.with()` to create a child logger that attaches properties to every\nsubsequent log call:\n\n~~~~ typescript\nconst reqLogger = logger.with({ requestId, userId });\nreqLogger.info(\"Processing order {orderId}\", { orderId });\n\u002F\u002F Log record will contain requestId, userId, AND orderId\n~~~~\n\n### Implicit context (request tracing)\n\nUse `withContext()` to propagate context across an entire call stack without\nthreading loggers manually.  Requires `contextLocalStorage` in configuration:\n\n~~~~ typescript\nimport { configure, getConsoleSink, withContext } from \"@logtape\u002Flogtape\";\nimport { AsyncLocalStorage } from \"node:async_hooks\";\n\nawait configure({\n  sinks: { console: getConsoleSink() },\n  loggers: [{ category: \"app\", sinks: [\"console\"] }],\n  contextLocalStorage: new AsyncLocalStorage(),\n});\n\nfunction handleRequest(req: Request) {\n  withContext({ requestId: crypto.randomUUID() }, () => {\n    \u002F\u002F All logs inside this callback automatically include requestId\n    processRequest(req);\n  });\n}\n~~~~\n\n> **Note:** Implicit contexts are not available in browsers yet.\n\n### Lazy evaluation\n\nWrap expensive computations with `lazy()` so they only run when the level is\nenabled:\n\n~~~~ typescript\nimport { getLogger, lazy } from \"@logtape\u002Flogtape\";\n\nconst logger = getLogger([\"my-app\"]);\nlogger.debug(\"System state: {state}\", {\n  state: lazy(() => JSON.stringify(getExpensiveState())),\n});\n~~~~\n\nFor structured data, pass a callback as the second argument:\n\n~~~~ typescript\nlogger.debug(\"Diagnostics\", () => ({\n  heap: process.memoryUsage().heapUsed,\n  uptime: process.uptime(),\n}));\n~~~~\n\nFor **async** lazy evaluation, pass an async callback and `await` the result:\n\n~~~~ typescript\nawait logger.info(\"User details\", async () => ({\n  user: await fetchUserDetails(),\n}));\n~~~~\n\nFor multiple expensive log calls, use `isEnabledFor()`:\n\n~~~~ typescript\nif (logger.isEnabledFor(\"debug\")) {\n  const snapshot = await captureExpensiveSnapshot();\n  logger.debug(\"Snapshot: {data}\", { data: snapshot });\n}\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Flazy.md> and\n\u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fcontexts.md> for details.\n\n\nLogging errors\n--------------\n\nPass `Error` objects directly to `error()` or `fatal()`.  You can attach\nextra properties as a second argument:\n\n~~~~ typescript\ntry {\n  await riskyOperation();\n} catch (error) {\n  logger.error(error, { operation: \"riskyOperation\", userId });\n}\n~~~~\n\n\nSinks and formatters\n--------------------\n\n### Built-in sinks\n\n~~~~ typescript\nimport {\n  configure,\n  getConsoleSink,\n  getStreamSink,\n} from \"@logtape\u002Flogtape\";\n\nawait configure({\n  sinks: {\n    console: getConsoleSink(),\n    stderr: getStreamSink(Writable.toWeb(process.stderr)),\n  },\n  loggers: [{ category: \"app\", sinks: [\"console\"] }],\n});\n~~~~\n\n### Sink filters\n\nUse `withFilter()` to route different levels to different sinks:\n\n~~~~ typescript\nimport { configure, getConsoleSink, withFilter } from \"@logtape\u002Flogtape\";\n\nawait configure({\n  sinks: {\n    errorsOnly: withFilter(getConsoleSink(), \"error\"),\n    allLevels: getConsoleSink(),\n  },\n  loggers: [\n    { category: \"app\", sinks: [\"allLevels\", \"errorsOnly\"] },\n  ],\n});\n~~~~\n\n### Formatters\n\n~~~~ typescript\nimport {\n  configure,\n  getAnsiColorFormatter,\n  getConsoleSink,\n  getJsonLinesFormatter,\n  getLogfmtFormatter,\n} from \"@logtape\u002Flogtape\";\n\n\u002F\u002F Pretty ANSI-colored output for development\ngetConsoleSink({ formatter: getAnsiColorFormatter() });\n\n\u002F\u002F JSON Lines for production \u002F log aggregation\ngetConsoleSink({ formatter: getJsonLinesFormatter() });\n\n\u002F\u002F logfmt for readable structured logs\ngetConsoleSink({ formatter: getLogfmtFormatter() });\n~~~~\n\nFor even nicer development output, use `@logtape\u002Fpretty`:\n\n~~~~ typescript\nimport { getPrettyFormatter } from \"@logtape\u002Fpretty\";\n\ngetConsoleSink({ formatter: getPrettyFormatter() });\n~~~~\n\n### Disposal\n\nNon-blocking sinks and stream sinks hold resources.  In **edge functions** or\nshort-lived processes, explicitly dispose before exit:\n\n~~~~ typescript\nimport { dispose } from \"@logtape\u002Flogtape\";\n\n\u002F\u002F At shutdown\nawait dispose();\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fsinks.md> and\n\u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fformatters.md> for details.\n\n\nData redaction\n--------------\n\nUse `@logtape\u002Fredaction` to prevent sensitive data from reaching log output.\n\n### Pattern-based redaction (scans formatted text)\n\nWrap a formatter with `redactByPattern()` to catch data like emails, credit\ncard numbers, or JWTs anywhere in the log output:\n\n~~~~ typescript\nimport { defaultConsoleFormatter, getConsoleSink } from \"@logtape\u002Flogtape\";\nimport {\n  EMAIL_ADDRESS_PATTERN,\n  JWT_PATTERN,\n  redactByPattern,\n} from \"@logtape\u002Fredaction\";\n\nconst sink = getConsoleSink({\n  formatter: redactByPattern(defaultConsoleFormatter, [\n    EMAIL_ADDRESS_PATTERN,\n    JWT_PATTERN,\n  ]),\n});\n~~~~\n\nBuilt-in patterns: `EMAIL_ADDRESS_PATTERN`, `CREDIT_CARD_NUMBER_PATTERN`,\n`JWT_PATTERN`, `US_SSN_PATTERN`, `KR_RRN_PATTERN`.\n\n### Field-based redaction (removes\u002Freplaces properties by name)\n\nWrap a sink with `redactByField()` to strip sensitive fields from structured\nlog data before it reaches the sink:\n\n~~~~ typescript\nimport { getConsoleSink } from \"@logtape\u002Flogtape\";\nimport { redactByField } from \"@logtape\u002Fredaction\";\n\n\u002F\u002F Uses DEFAULT_REDACT_FIELDS (password, secret, token, etc.)\nconst sink = redactByField(getConsoleSink());\n\n\u002F\u002F Or customize with replacement instead of removal\nconst sink2 = redactByField(getConsoleSink(), {\n  fieldPatterns: [\u002Fpassword\u002Fi, \u002Fsecret\u002Fi, \u002Fapi[-_]?key\u002Fi],\n  action: () => \"[REDACTED]\",\n});\n~~~~\n\n### Combining both for maximum security\n\n~~~~ typescript\nconst sink = redactByField(\n  getConsoleSink({\n    formatter: redactByPattern(defaultConsoleFormatter, [\n      EMAIL_ADDRESS_PATTERN,\n      JWT_PATTERN,\n    ]),\n  }),\n);\n~~~~\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fredaction.md> for details.\n\n\nAdaptors for existing loggers\n-----------------------------\n\nIf the project already uses winston, Pino, or log4js, use an adaptor instead\nof `configure()`:\n\n~~~~ typescript\nimport { install } from \"@logtape\u002Fadaptor-winston\";\nimport winston from \"winston\";\n\nconst winstonLogger = winston.createLogger({ \u002F* ... *\u002F });\ninstall(winstonLogger);\n\u002F\u002F All LogTape logs now route through winston\n~~~~\n\nAvailable: `@logtape\u002Fadaptor-winston`, `@logtape\u002Fadaptor-pino`,\n`@logtape\u002Fadaptor-log4js`.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Fadaptors.md> for details.\n\n\nTesting\n-------\n\nFor tests, use `@logtape\u002Ftesting` and assert on collected records:\n\n~~~~ typescript\nimport { configure, getLogger, reset } from \"@logtape\u002Flogtape\";\nimport { createLogRecorder } from \"@logtape\u002Ftesting\";\n\nconst recorder = createLogRecorder();\n\ntry {\n  await configure({\n    sinks: { recorder: recorder.sink },\n    loggers: [\n      { category: \"test\", sinks: [\"recorder\"] },\n      { category: [\"logtape\", \"meta\"], sinks: [] },\n    ],\n  });\n\n  const logger = getLogger([\"test\"]);\n  logger.info(\"User {userId} logged in.\", { userId: \"u-123\" });\n\n  recorder.assertLogged({\n    category: \"test\",\n    level: \"info\",\n    message: \u002F^User .+ logged in\\.$\u002F,\n    properties: { userId: \"u-123\" },\n  });\n} finally {\n  await reset();\n}\n~~~~\n\nIf using `configureSync()`, reset with `resetSync()`:\n\n~~~~ typescript\nimport { configureSync, resetSync } from \"@logtape\u002Flogtape\";\n\nconfigureSync({ \u002F* ... *\u002F });\n\u002F\u002F ... test ...\nresetSync();\n~~~~\n\nAlways call `reset()` \u002F `resetSync()` in test teardown so that each test can\nconfigure independently.\n\nSee \u003Chttps:\u002F\u002Flogtape.org\u002Fmanual\u002Ftesting.md> for more patterns.\n\n\nAvailable packages\n------------------\n\n### Sink packages\n\n| Package                     | Description            |\n| --------------------------- | ---------------------- |\n| `@logtape\u002Ffile`             | File and rotating file |\n| `@logtape\u002Fotel`             | OpenTelemetry          |\n| `@logtape\u002Fsentry`           | Sentry                 |\n| `@logtape\u002Fsyslog`           | Syslog                 |\n| `@logtape\u002Fcloudwatch-logs`  | AWS CloudWatch Logs    |\n| `@logtape\u002Fwindows-eventlog` | Windows Event Log      |\n\n### Framework integrations\n\n| Package                 | Description               |\n| ----------------------- | ------------------------- |\n| `@logtape\u002Fdrizzle-orm`  | Drizzle ORM query logging |\n| `@logtape\u002Felysia`       | Elysia HTTP logging       |\n| `@logtape\u002Fexpress`      | Express HTTP logging      |\n| `@logtape\u002Ffastify`      | Fastify HTTP logging      |\n| `@logtape\u002Fgraphql-yoga` | GraphQL Yoga logging      |\n| `@logtape\u002Fhono`         | Hono HTTP logging         |\n| `@logtape\u002Fkoa`          | Koa HTTP logging          |\n\n### Formatters\n\n| Package              | Description              |\n| -------------------- | ------------------------ |\n| `@logtape\u002Fpretty`    | Pretty console formatter |\n| `@logtape\u002Fredaction` | Sensitive data redaction |\n\n### Testing\n\n| Package            | Description                  |\n| ------------------ | ---------------------------- |\n| `@logtape\u002Ftesting` | Log recording and assertions |\n\n### Adaptors (for existing loggers)\n\n| Package                    | Description           |\n| -------------------------- | --------------------- |\n| `@logtape\u002Fadaptor-pino`    | Pino compatibility    |\n| `@logtape\u002Fadaptor-winston` | Winston compatibility |\n| `@logtape\u002Fadaptor-log4js`  | log4js compatibility  |\n\n\nCommon mistakes\n---------------\n\n### Using template literals for structured data\n\n~~~~ typescript\n\u002F\u002F WRONG: template literals don't produce structured data\nlogger.info`User ${userId} performed ${action}`;\n\n\u002F\u002F CORRECT: use placeholders for structured, searchable logs\nlogger.info(\"User {userId} performed {action}\", { userId, action });\n~~~~\n\n### String concatenation\n\n~~~~ typescript\n\u002F\u002F WRONG: loses structure, always evaluates\nlogger.info(\"User \" + userId + \" logged in from \" + ip);\n\n\u002F\u002F CORRECT\nlogger.info(\"User {userId} logged in from {ip}\", { userId, ip });\n~~~~\n\n### Calling `configure()` in library code\n\n~~~~ typescript\n\u002F\u002F WRONG: library must never configure LogTape\nimport { configure } from \"@logtape\u002Flogtape\";\nawait configure({ \u002F* ... *\u002F });  \u002F\u002F Don't do this in a library!\n\n\u002F\u002F CORRECT: just use getLogger()\nimport { getLogger } from \"@logtape\u002Flogtape\";\nconst logger = getLogger([\"my-lib\"]);\n~~~~\n\n### Forgetting to `await configure()`\n\n~~~~ typescript\n\u002F\u002F WRONG: configure() returns a Promise; without await, logging may\n\u002F\u002F not work when you expect it to\nconfigure({ \u002F* ... *\u002F });\n\n\u002F\u002F CORRECT\nawait configure({ \u002F* ... *\u002F });\n\n\u002F\u002F Or use the synchronous variant if you can't await\nconfigureSync({ \u002F* ... *\u002F });\n~~~~\n\n### Mixing async\u002Fsync configure and reset\n\n~~~~ typescript\n\u002F\u002F WRONG: mismatched pair causes errors\nawait configure({ \u002F* ... *\u002F });\nresetSync();  \u002F\u002F Can't sync-reset an async config!\n\n\u002F\u002F CORRECT: match configure and reset variants\nawait configure({ \u002F* ... *\u002F });\nawait reset();\n\n\u002F\u002F Or:\nconfigureSync({ \u002F* ... *\u002F });\nresetSync();\n~~~~\n\n### Using `console.log` alongside LogTape\n\n~~~~ typescript\n\u002F\u002F WRONG: bypasses LogTape's filtering, formatting, and routing\nconsole.log(\"User logged in:\", userId);\n\n\u002F\u002F CORRECT: use the logger so the message goes through configured sinks\nlogger.info(\"User {userId} logged in\", { userId });\n~~~~\n\n### Flat categories\n\n~~~~ typescript\n\u002F\u002F WRONG: single flat string prevents granular filtering\nconst logger = getLogger(\"myapp\");\n\n\u002F\u002F CORRECT: hierarchical array enables per-module control\nconst logger = getLogger([\"myapp\", \"auth\", \"oauth\"]);\n~~~~\n\n### Logging sensitive data without redaction\n\n~~~~ typescript\n\u002F\u002F WRONG: password ends up in log files\nlogger.info(\"Login attempt for {email} with {password}\", { email, password });\n\n\u002F\u002F CORRECT: never log secrets; use @logtape\u002Fredaction if needed\nlogger.info(\"Login attempt for {email}\", { email });\n~~~~\n\n\nBest practices summary\n----------------------\n\n -  One `configure()` or `configureSync()` call at startup\n -  Always `await configure()`; never `await configureSync()`\n -  Match reset variant to configure variant\n -  Hierarchical array categories (e.g., `[\"app\", \"module\", \"sub\"]`)\n -  Structured messages with named placeholders, not string interpolation\n -  `lazy()` or callback for expensive computations\n -  `logger.with()` for request-scoped context\n -  `withContext()` + `AsyncLocalStorage` for implicit context propagation\n -  `error`\u002F`fatal` only for real failures\n -  Libraries: never configure, just `getLogger()`\n -  Tests: `reset()` \u002F `resetSync()` in teardown, buffer sink for assertions\n -  Never log sensitive data (passwords, tokens, PII)\n -  Use `dispose()` \u002F `disposeSync()` in edge functions or short-lived\n    processes\n",{"name":5,"license":15,"description":24},"Use this skill when writing any code that uses LogTape for logging in JavaScript or TypeScript.  Covers getting loggers, the structured message syntax, configuration, library author rules, context, lazy evaluation, testing, and common mistakes to avoid.  Trigger whenever the user is adding logging to a project, debugging log output, or integrating LogTape with a framework.\n","main","dea450cfd9df78b5cf721964ef178a75cea55cbb","skills\u002F05-implementation-loop\u002Flogtape",2,"https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills","https:\u002F\u002Fmarcioaltoe.github.io\u002Fskills\u002F","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe","Senior Software Engineer · Backend, Systems & AI","2026-11-14 18:29:56",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add marcioaltoe\u002Fskills --skill logtape",{"tool":40,"command":41},"bunx","bunx skills add marcioaltoe\u002Fskills --skill logtape",{"tool":43,"command":44},"pnpm","pnpm dlx skills add marcioaltoe\u002Fskills --skill logtape","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F05-implementation-loop\u002Flogtape\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M72YNVSF4JTTQG3YTR9QNT4Z","startup-validator","Comprehensive startup idea validation and market analysis tool. Use when users need to evaluate a startup idea, assess market fit, analyze competition, validate problem-solution fit, or determine market positioning. Triggers include requests to \"validate my startup idea\", \"analyze market opportunity\", \"check if there's demand for\", \"research competition for\", \"evaluate business idea\", or \"see if my idea is viable\". Provides data-driven analysis using web search, market frameworks, competitive research, and positioning recommendations.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fstartup-validator\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":56},"01M72YNN34B4MYKEX1X6BB1NS1","positioning-icp","When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer persona,' 'enrichment signals,' 'market positioning,' or 'competitive positioning.' This skill covers market positioning, ICP definition, messaging architecture, and PMF validation for AI-native products. Do NOT use for technical implementation, code review, or software architecture.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fpositioning-icp\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":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":56},"01M72YNG8XJ4RHRB5DQMCY9C1N","copywriting","When the user wants to write or rewrite page copy (homepage, landing, pricing, feature), or asks which headline, promise, or message to lead with. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for. Claims must be supportable; a declined claim names the evidence that would unlock it. No AI tells like 'it's not X, it's Y' or 'no X, no Y, no Z'. For editing, see copy-editing. For emails, see emails. For the offer, see offers.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fcopywriting\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"01M72YNBF4JMQ4VCFHTW0WS6SD","business-storyteller","Transforms technical work into persuasive business-language documents for non-technical stakeholders, including internal announcements, approval proposals, incident explainers, technical-debt cases, product explainers, and investor or partner memos. Use when the user asks to present technical work to the company, explain software to business teams, write a business case, make an approval document, or convert a technical artifact into stakeholder communication in the requested language. Do not use for READMEs, specs, ADRs, external marketing pages, or customer-facing sales copy.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fbusiness-storyteller\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"01M72YN8NQ6QR0GHX2A8YW2K4T","brand-storytelling","Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fbrand-storytelling\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":56},"01M72YN3CJH7CKPF4AXNY79Q9S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F09-learning-loop\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F09-learning-loop\u002Fskill-creator\u002FSKILL.md",[],[]]