[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJ28GD2S8KCXNFZ4A3VXP8":3,"skill-same:01M7EJ28GD2S8KCXNFZ4A3VXP8":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7EJ28GD2S8KCXNFZ4A3VXP8","eventa",null,"Guide for using @moeru\u002Feventa — a transport-aware event library powering ergonomic RPC and streaming flows. Use this skill whenever the user imports from '@moeru\u002Feventa', mentions eventa, needs cross-process\u002Fcross-thread event communication (Electron IPC, Web Workers, WebSocket, BroadcastChannel, EventEmitter, EventTarget, Worker Threads), wants to define type-safe events with RPC invoke patterns, needs streaming RPC (server-streaming, client-streaming, or bidirectional), or asks about transport-agnostic event abstractions. Also use when the user discusses alternatives to birpc or async-call-rpc.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Feventa\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: eventa\ndescription: >-\n  Guide for using @moeru\u002Feventa — a transport-aware event library powering ergonomic RPC\n  and streaming flows. Use this skill whenever the user imports from '@moeru\u002Feventa',\n  mentions eventa, needs cross-process\u002Fcross-thread event communication (Electron IPC,\n  Web Workers, WebSocket, BroadcastChannel, EventEmitter, EventTarget, Worker Threads),\n  wants to define type-safe events with RPC invoke patterns, needs streaming RPC\n  (server-streaming, client-streaming, or bidirectional), or asks about transport-agnostic\n  event abstractions. Also use when the user discusses alternatives to birpc or async-call-rpc.\nlicense: MIT\nmetadata:\n  author: moeru-ai\n  version: \"1.0.0\"\n---\n\n# @moeru\u002Feventa\n\nTransport-aware events powering ergonomic RPC and streaming flows.\n\n## Core Concepts\n\nEventa is built around three ideas:\n\n1. **Events are first-class** — define typed events once, use them everywhere\n2. **Transports are swappable** — the same event definitions work across Electron IPC, WebSocket, Web Workers, BroadcastChannel, EventEmitter, EventTarget, and Worker Threads\n3. **RPC is just events** — invoke\u002Fstream patterns are composed from the same event primitives\n\n## API Quick Reference\n\n### Event Definition & Context\n\n```ts\nimport { createContext, defineEventa } from '@moeru\u002Feventa'\n\n\u002F\u002F Define a typed event (the generic is the payload type)\nconst move = defineEventa\u003C{ x: number, y: number }>()\n\n\u002F\u002F Create a base context (in-memory, useful for same-process communication)\nconst ctx = createContext()\n\n\u002F\u002F Emit and listen\nctx.emit(move, { x: 100, y: 200 })\nctx.on(move, ({ body }) => console.log(body.x, body.y))\n```\n\n### Unary RPC (Invoke)\n\n```ts\nimport { createContext, defineInvoke, defineInvokeEventa, defineInvokeHandler } from '@moeru\u002Feventa'\n\nconst ctx = createContext()\n\n\u002F\u002F defineInvokeEventa\u003CResponseType, RequestType>(optionalName)\nconst echo = defineInvokeEventa\u003C{ output: string }, { input: string }>('rpc:echo')\n\n\u002F\u002F Register handler (server side)\ndefineInvokeHandler(ctx, echo, ({ input }) => ({ output: input.toUpperCase() }))\n\n\u002F\u002F Create invoke function (client side)\nconst invokeEcho = defineInvoke(ctx, echo)\nconst result = await invokeEcho({ input: 'hello' }) \u002F\u002F { output: 'HELLO' }\n```\n\n### Streaming RPC (Server-Streaming)\n\n```ts\nimport { createContext, defineInvokeEventa, defineStreamInvoke, defineStreamInvokeHandler, toStreamHandler } from '@moeru\u002Feventa'\n\nconst ctx = createContext()\nconst sync = defineInvokeEventa\u003C\n  { type: 'progress' | 'result', value: number },\n  { jobId: string }\n>('rpc:sync')\n\n\u002F\u002F Generator-style handler\ndefineStreamInvokeHandler(ctx, sync, async function* ({ jobId }) {\n  for (let i = 1; i \u003C= 5; i++) {\n    yield { type: 'progress' as const, value: i * 20 }\n  }\n  yield { type: 'result' as const, value: 100 }\n})\n\n\u002F\u002F Or imperative style with toStreamHandler\ndefineStreamInvokeHandler(ctx, sync, toStreamHandler(async ({ payload, emit }) => {\n  emit({ type: 'progress', value: 0 })\n  emit({ type: 'result', value: 100 })\n}))\n\n\u002F\u002F Consume as async iterator\nconst stream = defineStreamInvoke(ctx, sync)\nfor await (const update of stream({ jobId: 'import' })) {\n  console.log(update.type, update.value)\n}\n```\n\n### Client-Streaming (Stream Input, Unary Output)\n\n```ts\nconst recordRoute = defineInvokeEventa\u003C\n  { distance: number, points: number },\n  ReadableStream\u003C{ lat: number, lng: number }>\n>('rpc:record-route')\n\ndefineInvokeHandler(ctx, recordRoute, async (stream) => {\n  let points = 0\n  for await (const _ of stream) points += 1\n  return { distance: points * 10, points }\n})\n\nconst invoke = defineInvoke(ctx, recordRoute)\nconst input = new ReadableStream({\n  start(c) { c.enqueue({ lat: 0, lng: 0 }); c.enqueue({ lat: 1, lng: 1 }); c.close() },\n})\nawait invoke(input)\n```\n\n### Bidirectional Streaming\n\n```ts\nconst routeChat = defineInvokeEventa\u003C\n  { message: string },\n  ReadableStream\u003C{ message: string }>\n>('rpc:route-chat')\n\ndefineStreamInvokeHandler(ctx, routeChat, async function* (incoming) {\n  for await (const note of incoming) {\n    yield { message: `echo: ${note.message}` }\n  }\n})\n\nconst stream = defineStreamInvoke(ctx, routeChat)\nfor await (const note of stream(outgoing)) {\n  console.log(note.message)\n}\n```\n\n### Abort\u002FCancel\n\n```ts\n\u002F\u002F Client-side cancellation\nconst controller = new AbortController()\nconst promise = invokeMethod({ input: 'work' }, { signal: controller.signal })\ncontroller.abort('user cancelled')\n\n\u002F\u002F Server-side abort awareness\ndefineInvokeHandler(ctx, event, async ({ input }, options) => {\n  const signal = options?.abortController?.signal\n  if (signal?.aborted) return { output: 'aborted' }\n  signal?.addEventListener('abort', () => { \u002F* cleanup *\u002F }, { once: true })\n  return { output: `done: ${input}` }\n})\n```\n\n### Multi-hop Channels\n\nChannels form ordered routing chains. They carry events, unary invokes, every\nstream frame, and invocation cancellation through intermediate contexts.\n\n```ts\nimport { linkChannel, pipeChannel } from '@moeru\u002Feventa'\n\npipeChannel(a, b, c) \u002F\u002F a -> b -> c\nlinkChannel(a, b, c) \u002F\u002F a \u003C-> b \u003C-> c\n```\n\nThere is no direct `a` to `c` edge. Use multiple explicit pipes for fan-out.\nDisposing a channel removes its edges only; context abort never cascades across\na link. One connected graph must have one effective handler for each invoke\ndefinition.\n\nEach local emit creates an `EventaInner` whose `deliveryId` survives channel\nhops and transport serialization. Contexts suppress recently seen delivery IDs\nand stop forwarding when `hopsRemaining` reaches zero. Plugins may inspect the\nread-only inner value and transform or drop its Eventa, but may not replace routing\nidentity or hop state.\n\nFor iframe-to-server routing, connect the EventTarget-side context to the\nplugin's BroadcastChannel context, then connect the gateway's BroadcastChannel\ncontext to its WebSocket context. The adapters carry the inner value across the\nruntime boundaries; no directional forwarding markers are needed.\n\nContexts do not serialize concurrent `emit()` calls. Request and response\nstream pumps await each frame only to preserve per-invocation stream order;\ncancellation is routed independently and may arrive before request frames.\n\n### Bulk Registration (Shorthands)\n\n```ts\nconst events = {\n  double: defineInvokeEventa\u003Cnumber, number>(),\n  append: defineInvokeEventa\u003Cstring, string>(),\n}\n\ndefineInvokeHandlers(ctx, events, {\n  double: input => input * 2,\n  append: input => `${input}!`,\n})\n\nconst { double, append } = defineInvokes(ctx, events)\n```\n\n## Adapters\n\nEach adapter wraps a specific transport into an eventa context. The pattern is always:\n\n```ts\nimport { createContext } from '@moeru\u002Feventa\u002Fadapters\u002F\u003Cadapter-name>'\nconst { context } = createContext(transportInstance)\n```\n\n### Available Adapters\n\n| Adapter | Import Path | Transport |\n|---------|-------------|-----------|\n| Electron Main | `@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Fmain` | `ipcMain` + `webContents` |\n| Electron Renderer | `@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Frenderer` | `ipcRenderer` |\n| Web Worker (main) | `@moeru\u002Feventa\u002Fadapters\u002Fwebworkers` | `Worker` instance |\n| Web Worker (worker) | `@moeru\u002Feventa\u002Fadapters\u002Fwebworkers\u002Fworker` | `self` (worker global) |\n| Worker Threads (main) | `@moeru\u002Feventa\u002Fadapters\u002Fworker-threads` | Node.js `Worker` |\n| Worker Threads (worker) | `@moeru\u002Feventa\u002Fadapters\u002Fworker-threads\u002Fworker` | `parentPort` |\n| WebSocket Client | `@moeru\u002Feventa\u002Fadapters\u002Fwebsocket\u002Fnative` | `WebSocket` |\n| WebSocket Server (H3) | `@moeru\u002Feventa\u002Fadapters\u002Fwebsocket\u002Fh3` | H3 WebSocket hooks |\n| BroadcastChannel | `@moeru\u002Feventa\u002Fadapters\u002Fbroadcast-channel` | `BroadcastChannel` |\n| EventTarget | `@moeru\u002Feventa\u002Fadapters\u002Fevent-target` | `EventTarget` |\n| EventEmitter | `@moeru\u002Feventa\u002Fadapters\u002Fevent-emitter` | Node.js `EventEmitter` |\n\n### Adapter Usage Pattern (Electron Example)\n\n```ts\n\u002F\u002F shared\u002Fevents.ts — define events once\nimport { defineInvokeEventa } from '@moeru\u002Feventa'\nexport const readdir = defineInvokeEventa\u003C{ dirs: string[] }, { path: string }>('fs:readdir')\n\n\u002F\u002F main.ts — register handler\nimport { createContext } from '@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Fmain'\nconst { context } = createContext(ipcMain, mainWindow.webContents)\ndefineInvokeHandler(context, readdir, async ({ path }) => ({ dirs: await fs.readdir(path) }))\n\n\u002F\u002F renderer.ts (preload) — call it\nimport { createContext } from '@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Frenderer'\nconst { context } = createContext(ipcRenderer)\nconst invokeReaddir = defineInvoke(context, readdir)\nconst result = await invokeReaddir({ path: '\u002Fusr' })\n```\n\n## Advanced Features\n\n- **Delivery routing**: `EventaInner\u003CT>` preserves delivery identity and hop budget across channels and adapters\n- **Match expressions**: `matchBy(glob)`, `matchBy(regex)`, `and(...)`, `or(...)` for event filtering\n- **WebSocket lifecycle**: `wsConnectedEvent` and `wsDisconnectedEvent` from the native adapter\n\n## Key Rules\n\n1. Always define events in a shared module — both sides import the same event definition for type safety\n2. `defineInvokeEventa\u003CRes, Req>()` — Response type comes first, Request type second\n3. Handlers can throw errors safely — eventa propagates them to the caller\n4. Validate data at the edges — eventa forwards whatever payload you emit\n5. Install only the peer dependencies you need (electron, h3, web-worker are all optional)\n\n## Documentation\n\nFor the latest API reference, use context7 to query `@moeru\u002Feventa` documentation.\n","# @moeru\u002Feventa\n\nTransport-aware events powering ergonomic RPC and streaming flows.\n\n## Core Concepts\n\nEventa is built around three ideas:\n\n1. **Events are first-class** — define typed events once, use them everywhere\n2. **Transports are swappable** — the same event definitions work across Electron IPC, WebSocket, Web Workers, BroadcastChannel, EventEmitter, EventTarget, and Worker Threads\n3. **RPC is just events** — invoke\u002Fstream patterns are composed from the same event primitives\n\n## API Quick Reference\n\n### Event Definition & Context\n\n```ts\nimport { createContext, defineEventa } from '@moeru\u002Feventa'\n\n\u002F\u002F Define a typed event (the generic is the payload type)\nconst move = defineEventa\u003C{ x: number, y: number }>()\n\n\u002F\u002F Create a base context (in-memory, useful for same-process communication)\nconst ctx = createContext()\n\n\u002F\u002F Emit and listen\nctx.emit(move, { x: 100, y: 200 })\nctx.on(move, ({ body }) => console.log(body.x, body.y))\n```\n\n### Unary RPC (Invoke)\n\n```ts\nimport { createContext, defineInvoke, defineInvokeEventa, defineInvokeHandler } from '@moeru\u002Feventa'\n\nconst ctx = createContext()\n\n\u002F\u002F defineInvokeEventa\u003CResponseType, RequestType>(optionalName)\nconst echo = defineInvokeEventa\u003C{ output: string }, { input: string }>('rpc:echo')\n\n\u002F\u002F Register handler (server side)\ndefineInvokeHandler(ctx, echo, ({ input }) => ({ output: input.toUpperCase() }))\n\n\u002F\u002F Create invoke function (client side)\nconst invokeEcho = defineInvoke(ctx, echo)\nconst result = await invokeEcho({ input: 'hello' }) \u002F\u002F { output: 'HELLO' }\n```\n\n### Streaming RPC (Server-Streaming)\n\n```ts\nimport { createContext, defineInvokeEventa, defineStreamInvoke, defineStreamInvokeHandler, toStreamHandler } from '@moeru\u002Feventa'\n\nconst ctx = createContext()\nconst sync = defineInvokeEventa\u003C\n  { type: 'progress' | 'result', value: number },\n  { jobId: string }\n>('rpc:sync')\n\n\u002F\u002F Generator-style handler\ndefineStreamInvokeHandler(ctx, sync, async function* ({ jobId }) {\n  for (let i = 1; i \u003C= 5; i++) {\n    yield { type: 'progress' as const, value: i * 20 }\n  }\n  yield { type: 'result' as const, value: 100 }\n})\n\n\u002F\u002F Or imperative style with toStreamHandler\ndefineStreamInvokeHandler(ctx, sync, toStreamHandler(async ({ payload, emit }) => {\n  emit({ type: 'progress', value: 0 })\n  emit({ type: 'result', value: 100 })\n}))\n\n\u002F\u002F Consume as async iterator\nconst stream = defineStreamInvoke(ctx, sync)\nfor await (const update of stream({ jobId: 'import' })) {\n  console.log(update.type, update.value)\n}\n```\n\n### Client-Streaming (Stream Input, Unary Output)\n\n```ts\nconst recordRoute = defineInvokeEventa\u003C\n  { distance: number, points: number },\n  ReadableStream\u003C{ lat: number, lng: number }>\n>('rpc:record-route')\n\ndefineInvokeHandler(ctx, recordRoute, async (stream) => {\n  let points = 0\n  for await (const _ of stream) points += 1\n  return { distance: points * 10, points }\n})\n\nconst invoke = defineInvoke(ctx, recordRoute)\nconst input = new ReadableStream({\n  start(c) { c.enqueue({ lat: 0, lng: 0 }); c.enqueue({ lat: 1, lng: 1 }); c.close() },\n})\nawait invoke(input)\n```\n\n### Bidirectional Streaming\n\n```ts\nconst routeChat = defineInvokeEventa\u003C\n  { message: string },\n  ReadableStream\u003C{ message: string }>\n>('rpc:route-chat')\n\ndefineStreamInvokeHandler(ctx, routeChat, async function* (incoming) {\n  for await (const note of incoming) {\n    yield { message: `echo: ${note.message}` }\n  }\n})\n\nconst stream = defineStreamInvoke(ctx, routeChat)\nfor await (const note of stream(outgoing)) {\n  console.log(note.message)\n}\n```\n\n### Abort\u002FCancel\n\n```ts\n\u002F\u002F Client-side cancellation\nconst controller = new AbortController()\nconst promise = invokeMethod({ input: 'work' }, { signal: controller.signal })\ncontroller.abort('user cancelled')\n\n\u002F\u002F Server-side abort awareness\ndefineInvokeHandler(ctx, event, async ({ input }, options) => {\n  const signal = options?.abortController?.signal\n  if (signal?.aborted) return { output: 'aborted' }\n  signal?.addEventListener('abort', () => { \u002F* cleanup *\u002F }, { once: true })\n  return { output: `done: ${input}` }\n})\n```\n\n### Multi-hop Channels\n\nChannels form ordered routing chains. They carry events, unary invokes, every\nstream frame, and invocation cancellation through intermediate contexts.\n\n```ts\nimport { linkChannel, pipeChannel } from '@moeru\u002Feventa'\n\npipeChannel(a, b, c) \u002F\u002F a -> b -> c\nlinkChannel(a, b, c) \u002F\u002F a \u003C-> b \u003C-> c\n```\n\nThere is no direct `a` to `c` edge. Use multiple explicit pipes for fan-out.\nDisposing a channel removes its edges only; context abort never cascades across\na link. One connected graph must have one effective handler for each invoke\ndefinition.\n\nEach local emit creates an `EventaInner` whose `deliveryId` survives channel\nhops and transport serialization. Contexts suppress recently seen delivery IDs\nand stop forwarding when `hopsRemaining` reaches zero. Plugins may inspect the\nread-only inner value and transform or drop its Eventa, but may not replace routing\nidentity or hop state.\n\nFor iframe-to-server routing, connect the EventTarget-side context to the\nplugin's BroadcastChannel context, then connect the gateway's BroadcastChannel\ncontext to its WebSocket context. The adapters carry the inner value across the\nruntime boundaries; no directional forwarding markers are needed.\n\nContexts do not serialize concurrent `emit()` calls. Request and response\nstream pumps await each frame only to preserve per-invocation stream order;\ncancellation is routed independently and may arrive before request frames.\n\n### Bulk Registration (Shorthands)\n\n```ts\nconst events = {\n  double: defineInvokeEventa\u003Cnumber, number>(),\n  append: defineInvokeEventa\u003Cstring, string>(),\n}\n\ndefineInvokeHandlers(ctx, events, {\n  double: input => input * 2,\n  append: input => `${input}!`,\n})\n\nconst { double, append } = defineInvokes(ctx, events)\n```\n\n## Adapters\n\nEach adapter wraps a specific transport into an eventa context. The pattern is always:\n\n```ts\nimport { createContext } from '@moeru\u002Feventa\u002Fadapters\u002F\u003Cadapter-name>'\nconst { context } = createContext(transportInstance)\n```\n\n### Available Adapters\n\n| Adapter | Import Path | Transport |\n|---------|-------------|-----------|\n| Electron Main | `@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Fmain` | `ipcMain` + `webContents` |\n| Electron Renderer | `@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Frenderer` | `ipcRenderer` |\n| Web Worker (main) | `@moeru\u002Feventa\u002Fadapters\u002Fwebworkers` | `Worker` instance |\n| Web Worker (worker) | `@moeru\u002Feventa\u002Fadapters\u002Fwebworkers\u002Fworker` | `self` (worker global) |\n| Worker Threads (main) | `@moeru\u002Feventa\u002Fadapters\u002Fworker-threads` | Node.js `Worker` |\n| Worker Threads (worker) | `@moeru\u002Feventa\u002Fadapters\u002Fworker-threads\u002Fworker` | `parentPort` |\n| WebSocket Client | `@moeru\u002Feventa\u002Fadapters\u002Fwebsocket\u002Fnative` | `WebSocket` |\n| WebSocket Server (H3) | `@moeru\u002Feventa\u002Fadapters\u002Fwebsocket\u002Fh3` | H3 WebSocket hooks |\n| BroadcastChannel | `@moeru\u002Feventa\u002Fadapters\u002Fbroadcast-channel` | `BroadcastChannel` |\n| EventTarget | `@moeru\u002Feventa\u002Fadapters\u002Fevent-target` | `EventTarget` |\n| EventEmitter | `@moeru\u002Feventa\u002Fadapters\u002Fevent-emitter` | Node.js `EventEmitter` |\n\n### Adapter Usage Pattern (Electron Example)\n\n```ts\n\u002F\u002F shared\u002Fevents.ts — define events once\nimport { defineInvokeEventa } from '@moeru\u002Feventa'\nexport const readdir = defineInvokeEventa\u003C{ dirs: string[] }, { path: string }>('fs:readdir')\n\n\u002F\u002F main.ts — register handler\nimport { createContext } from '@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Fmain'\nconst { context } = createContext(ipcMain, mainWindow.webContents)\ndefineInvokeHandler(context, readdir, async ({ path }) => ({ dirs: await fs.readdir(path) }))\n\n\u002F\u002F renderer.ts (preload) — call it\nimport { createContext } from '@moeru\u002Feventa\u002Fadapters\u002Felectron\u002Frenderer'\nconst { context } = createContext(ipcRenderer)\nconst invokeReaddir = defineInvoke(context, readdir)\nconst result = await invokeReaddir({ path: '\u002Fusr' })\n```\n\n## Advanced Features\n\n- **Delivery routing**: `EventaInner\u003CT>` preserves delivery identity and hop budget across channels and adapters\n- **Match expressions**: `matchBy(glob)`, `matchBy(regex)`, `and(...)`, `or(...)` for event filtering\n- **WebSocket lifecycle**: `wsConnectedEvent` and `wsDisconnectedEvent` from the native adapter\n\n## Key Rules\n\n1. Always define events in a shared module — both sides import the same event definition for type safety\n2. `defineInvokeEventa\u003CRes, Req>()` — Response type comes first, Request type second\n3. Handlers can throw errors safely — eventa propagates them to the caller\n4. Validate data at the edges — eventa forwards whatever payload you emit\n5. Install only the peer dependencies you need (electron, h3, web-worker are all optional)\n\n## Documentation\n\nFor the latest API reference, use context7 to query `@moeru\u002Feventa` documentation.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"moeru-ai","1.0.0","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Feventa",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill eventa",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill eventa",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill eventa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Feventa\u002FSKILL.md",true,[],[50,58,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":57},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":57},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":57},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":57},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":57},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]