[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DFGAHFQSZR41ZGQM8B932":3,"skill-same:01M73DFGAHFQSZR41ZGQM8B932":62},{"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":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M73DFGAHFQSZR41ZGQM8B932","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Flambda-lang\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Flambda-lang",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill lambda-lang",{"tool":54,"command":55},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill lambda-lang",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill lambda-lang","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Flambda-lang\u002FSKILL.md",true,[],[63,71,78,86,94,102],{"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":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":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":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":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":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]