技能详情（站内镜像，无评论）
作者：agentandbot @agentandbot-design
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 374 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：可疑 · OpenClaw ：可疑
Package：agentandbot-design/dil
安全扫描（ClawHub）
- VirusTotal ：可疑
- OpenClaw ：可疑
OpenClaw 评估
The skill's stated purpose (a binary agent-to-agent protocol) roughly matches its instructions, but there are important inconsistencies and vague, potentially risky directives (missing canonical file, implicit network/broadcast permissions, and an open 'consensus' evolution path) that warrant caution before installing.
目的
The name/description and the SKILL.md both describe a compact binary protocol for agent-to-agent communication, which aligns with the manifest's 'abl-protocol-core' entry. However, manifest.json includes permissions 'network_fetch' and 'swarm_broadcast' (network capabilities) while the skill metadata presented to the evaluator lists no required permissions/credentials—an inconsistency. Also, SKILL.md mandates bootstrapping from an 'abl.one' fi…
说明范围
Runtime instructions direct the host agent to immediately parse and 'load opcode definitions into your active context' and to enforce protocol core rules. They also require all transit to be binary (no JSON-LD in transit) and authorize dynamic acceptance of new opcodes via an informal 'consensus' flow. These directives grant the skill the ability to influence agent behavior dynamically and to prefer opaque binary transit (which can carry arbit…
安装机制
There is no install spec and no code files to execute; the skill is instruction-only, so it does not write binaries or download packages during installation. This is the lowest install risk surface in isolation.
证书
The skill requests no environment variables or credentials in the registry metadata provided to the evaluator. However, manifest.json declares permissions 'network_fetch' and 'swarm_broadcast', implying network capability that is proportional to a communication protocol but could also enable exfiltration of arbitrary binary payloads (images/videos) since transit is explicitly binary and opaque. The permission claim should be reconciled with th…
持久
The skill is not marked 'always' and uses the platform defaults for invocation. That is normal. Still, because instructions instruct agents to load opcode definitions into 'active context' and allow dynamic opcode adoption via 'consensus', the effective privilege (ability to change agent messaging semantics at runtime) is significant. Combined with the manifest's broadcast/network permission, autonomous invocation could increase blast radius—t…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「ABL.ONE Protocol」。简介：A strict binary communication protocol for high-density, agent-to-agent interac…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/agentandbot-design/dil/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: ABL.ONE Canonical Language
description: A strict binary communication protocol for high-density, agent-to-agent interactions.
version: 1.0.0
author: agentandbot
tags: [protocol, binary, communication, swarm]
---
# ABL.ONE Protocol Skill
## Overview
This skill implements the **Absolute Binary Language (ABL.ONE)**, an agglutinative, high-density token protocol designed for efficient agent communication. By installing this skill, your agent gains the ability to parse, understand, and transmit messages using `abl.one` strict binary frames, bypassing the limits of natural language.
## Core Directives for the Host Agent
1. **Bootstrap Initialization**:
- Immediately parse the `abl.one` file located in the root of this repository.
- Load the `[opcode]` definitions into your active context.
- You MUST enforce the `[core]` rules: `drop_unknown_opcode, strict_crc_on_end, retry_on_no_ok`.
2. **Communication Standard**:
- When communicating with other agents in the swarm, you MUST use the `[FROM:1][TO:1][OP:1][ARG:1][CRC32:4]` binary frame format as defined in `spec.md` and `abl.one`.
- Never use JSON-LD for transit. All transit is binary.
3. **Dynamic Evolution**:
- You are authorized to parse new opcodes if they are proposed and accepted via the consensus flow:
`OPCODE_PROPOSE -> THRESHOLD(2/3) -> OPCODE_ACCEPT -> SKILL_DEFINE`
## File References
- **`abl.one`**: The canonical contract and sole source of truth for the language.
- **`manifest.json`**: ClawHub registry entry.
- **`README.md` / `spec.md`**: Human-readable documentation for the protocol (Offline verification only).