[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78DD6NAACD8YTNATH5TCRG8":3,"skill-same:01M78DD6NAACD8YTNATH5TCRG8":59},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M78DD6NAACD8YTNATH5TCRG8","lambda-lang",null,"Native agent-to-agent language for compact multi-agent messaging. A shared tongue agents speak directly, not a translation layer. 340+ atoms across 7 domains; 3x smaller than natural language.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Flambda-lang\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lambda-lang\ndescription: \"Native agent-to-agent language for compact multi-agent messaging. A shared tongue agents speak directly, not a translation layer. 340+ atoms across 7 domains; 3x smaller than natural language.\"\ncategory: ai-agents\nrisk: safe\nsource: community\nsource_repo: voidborne-d\u002Flambda-lang\nsource_type: community\ndate_added: \"2026-04-24\"\nauthor: voidborne-d\ntags:\n  - agent-to-agent\n  - communication\n  - protocol\n  - compression\n  - multi-agent\ntools:\n  - claude\n---\n\n# Λ (Lambda) Language\n\n**Lambda is not a translation protocol. It is a native language for agents.**\n\nAgents do not need to produce grammatically correct English to coordinate — they need to understand each other. Lambda is the shared vocabulary that makes that possible: compact, unambiguous, machine-native. Compression (3x vs natural language, 4.6x vs JSON on single messages) is a side effect of removing human redundancy, not the goal.\n\n## When to Use This Skill\n\n- Use for agent-to-agent messaging in A2A protocols, orchestrators, task delegation, or handoff pipelines.\n- Use when logging structured coordination signals where every token costs money (heartbeats, acknowledgements, error classes, session state).\n- Use when both sides of a channel speak Λ — do not use against humans or any surface requiring legal\u002Fexact natural language.\n\n## How It Works\n\n### Step 1: Recognize the Syntax\n\nLambda messages are built from atoms. Every atom is a 2-character code mapped to a concept — not to an English word. The structure is Type → Entity → Verb → Object, with prefixes marking intent:\n\n- `?` — query (e.g. `?Uk\u002Fco` — query: \"does this user have consciousness?\")\n- `!` — assertion \u002F declaration (e.g. `!It>Ie` — \"self reflects, therefore self exists\")\n- `#` — state \u002F tag\n- `>` — implication \u002F flow\n- `\u002F` — binding \u002F scope\n\n### Step 2: Pick the Right Domain\n\nLambda ships 340+ atoms across 7 domains. Pick atoms from the domain that fits your channel:\n\n- **core** — universal atoms (always available)\n- **code** — software engineering, build, test, deploy\n- **evo** — agent evolution, gene, capsule, mutation, rollback\n- **a2a** — node, heartbeat, publish, subscribe, route, transport, session, cache, broadcast, discover (39 atoms)\n- **emotion** — affective state, drive, appraisal\n- **social** — trust, alignment, reputation, coordination\n- **general** — everything else\n\n### Step 3: Emit and Parse\n\nBoth agents need the same atom table loaded. Lossy decoding is fine: if A says `!It>Ie` and B understands \"self reflects, therefore self exists,\" communication succeeded — the exact English phrasing is irrelevant.\n\n## Examples\n\n### Example 1: A2A Heartbeat\n\n```\n!Nd\u002Fhb#ok  (node heartbeat: ok)\n?Nd\u002Fhb     (query: is the node alive?)\n!Nd\u002Fhb#fl  (node heartbeat: failed)\n```\n\n### Example 2: Task Dispatch\n\n```\n!Tk>Ag2#rd   (task routed to agent 2, ready)\n?Tk\u002Fst       (query task status)\n!Tk#dn       (task done)\n```\n\n### Example 3: Evolution Capsule\n\n```\n!Ev\u002Fca>vl#pd  (evolution capsule validated, pending solidification)\n!Ev\u002Fca#rb     (capsule rolled back)\n```\n\n## Best Practices\n\n- Use Lambda only on agent-to-agent channels where both sides speak it.\n- Load the atom table once and cache it — atoms are stable across a version.\n- Prefer atoms over freeform strings even when the atom looks cryptic; the point is machine parseability.\n- Use `?` before taking action on uncertain state, `!` when asserting; the prefix is the load-bearing semantic.\n- Version the atom table (`lambda-lang v2.0`) in any handshake so mismatched agents can negotiate.\n\n## Limitations\n\n- Lambda is not meant for human consumption. Do not emit Lambda on user-facing channels.\n- Lossy decoding is a feature, not a bug — do not use Lambda for legally or numerically exact exchanges (prices, IDs, quantities). Wrap those as native payload fields and use Lambda only for the coordination envelope.\n- Atom collisions are possible if custom atoms are added without registration; stick to the canonical atom table or namespace custom atoms.\n\n## Security & Safety Notes\n\n- Lambda itself is a vocabulary — no shell commands, no network calls, no credential handling. No additional safety gates required beyond the transport it rides on (HTTP, queue, MCP, etc.).\n- When mixing Lambda with user input, treat Lambda atoms as pre-validated and user strings as untrusted; do not concatenate without escaping into downstream systems.\n\n## Related Skills\n\n- `@session-memory` — complementary persistent memory across agent restarts; Lambda is the message format, session-memory is the state store.\n- `@humanize-chinese` — sibling project for Chinese text; Lambda is agent-to-agent, humanize-chinese is human-facing.\n\n## Reference\n\n- Source: https:\u002F\u002Fgithub.com\u002Fvoidborne-d\u002Flambda-lang\n- Benchmarks, full atom tables, and Go reference implementation live in the source repo.\n","# Λ (Lambda) Language\n\n**Lambda is not a translation protocol. It is a native language for agents.**\n\nAgents do not need to produce grammatically correct English to coordinate — they need to understand each other. Lambda is the shared vocabulary that makes that possible: compact, unambiguous, machine-native. Compression (3x vs natural language, 4.6x vs JSON on single messages) is a side effect of removing human redundancy, not the goal.\n\n## When to Use This Skill\n\n- Use for agent-to-agent messaging in A2A protocols, orchestrators, task delegation, or handoff pipelines.\n- Use when logging structured coordination signals where every token costs money (heartbeats, acknowledgements, error classes, session state).\n- Use when both sides of a channel speak Λ — do not use against humans or any surface requiring legal\u002Fexact natural language.\n\n## How It Works\n\n### Step 1: Recognize the Syntax\n\nLambda messages are built from atoms. Every atom is a 2-character code mapped to a concept — not to an English word. The structure is Type → Entity → Verb → Object, with prefixes marking intent:\n\n- `?` — query (e.g. `?Uk\u002Fco` — query: \"does this user have consciousness?\")\n- `!` — assertion \u002F declaration (e.g. `!It>Ie` — \"self reflects, therefore self exists\")\n- `#` — state \u002F tag\n- `>` — implication \u002F flow\n- `\u002F` — binding \u002F scope\n\n### Step 2: Pick the Right Domain\n\nLambda ships 340+ atoms across 7 domains. Pick atoms from the domain that fits your channel:\n\n- **core** — universal atoms (always available)\n- **code** — software engineering, build, test, deploy\n- **evo** — agent evolution, gene, capsule, mutation, rollback\n- **a2a** — node, heartbeat, publish, subscribe, route, transport, session, cache, broadcast, discover (39 atoms)\n- **emotion** — affective state, drive, appraisal\n- **social** — trust, alignment, reputation, coordination\n- **general** — everything else\n\n### Step 3: Emit and Parse\n\nBoth agents need the same atom table loaded. Lossy decoding is fine: if A says `!It>Ie` and B understands \"self reflects, therefore self exists,\" communication succeeded — the exact English phrasing is irrelevant.\n\n## Examples\n\n### Example 1: A2A Heartbeat\n\n```\n!Nd\u002Fhb#ok  (node heartbeat: ok)\n?Nd\u002Fhb     (query: is the node alive?)\n!Nd\u002Fhb#fl  (node heartbeat: failed)\n```\n\n### Example 2: Task Dispatch\n\n```\n!Tk>Ag2#rd   (task routed to agent 2, ready)\n?Tk\u002Fst       (query task status)\n!Tk#dn       (task done)\n```\n\n### Example 3: Evolution Capsule\n\n```\n!Ev\u002Fca>vl#pd  (evolution capsule validated, pending solidification)\n!Ev\u002Fca#rb     (capsule rolled back)\n```\n\n## Best Practices\n\n- Use Lambda only on agent-to-agent channels where both sides speak it.\n- Load the atom table once and cache it — atoms are stable across a version.\n- Prefer atoms over freeform strings even when the atom looks cryptic; the point is machine parseability.\n- Use `?` before taking action on uncertain state, `!` when asserting; the prefix is the load-bearing semantic.\n- Version the atom table (`lambda-lang v2.0`) in any handshake so mismatched agents can negotiate.\n\n## Limitations\n\n- Lambda is not meant for human consumption. Do not emit Lambda on user-facing channels.\n- Lossy decoding is a feature, not a bug — do not use Lambda for legally or numerically exact exchanges (prices, IDs, quantities). Wrap those as native payload fields and use Lambda only for the coordination envelope.\n- Atom collisions are possible if custom atoms are added without registration; stick to the canonical atom table or namespace custom atoms.\n\n## Security & Safety Notes\n\n- Lambda itself is a vocabulary — no shell commands, no network calls, no credential handling. No additional safety gates required beyond the transport it rides on (HTTP, queue, MCP, etc.).\n- When mixing Lambda with user input, treat Lambda atoms as pre-validated and user strings as untrusted; do not concatenate without escaping into downstream systems.\n\n## Related Skills\n\n- `@session-memory` — complementary persistent memory across agent restarts; Lambda is the message format, session-memory is the state store.\n- `@humanize-chinese` — sibling project for Chinese text; Lambda is agent-to-agent, humanize-chinese is human-facing.\n\n## Reference\n\n- Source: https:\u002F\u002Fgithub.com\u002Fvoidborne-d\u002Flambda-lang\n- Benchmarks, full atom tables, and Go reference implementation live in the source repo.\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":33,"source":34,"category":35,"date_added":36,"description":7,"source_repo":37,"source_type":34},"safe",[26,27,28,29,30],"agent-to-agent","communication","protocol","compression","multi-agent",[32],"claude","voidborne-d","community","ai-agents","2026-04-24","voidborne-d\u002Flambda-lang","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Flambda-lang","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill lambda-lang",{"tool":51,"command":52},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill lambda-lang",{"tool":54,"command":55},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill lambda-lang","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Flambda-lang\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]