Encoding Format Advisor
v1.0.0Select a data encoding format (JSON, Protobuf, Thrift, or Avro) and design a schema evolution strategy that preserves backward and forward compatibility thro...
⭐ 0· 57·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (encoding format selection and schema-evolution advice) aligns with the inputs, artifacts, and outputs the skill declares (schema files, architecture docs, .proto/.thrift/.avsc files). No unrelated credentials, binaries, or install steps are requested.
Instruction Scope
SKILL.md instructs the agent to analyze provided schema files, code, and architecture docs and to produce a concrete recommendation and evolution plan — this stays within the stated purpose. One thing to note: the skill expects the agent to use Read and Write tools on whatever documents the user supplies, so the agent could read arbitrary project files if the user provides them; that is expected but users should avoid supplying unrelated sensitive files (secrets, credentials, private keys).
Install Mechanism
No install spec and no code files are present (instruction-only). Nothing will be downloaded or written to disk by an installer.
Credentials
The skill requests no environment variables, no credentials, and no config paths. The declared required tools (Read, Write, optional Grep) are proportional to document and code analysis tasks.
Persistence & Privilege
always is false and the skill does not request persistent privileges or modify other skills or system-wide settings. The skill may be invoked autonomously by agents (normal default), but it does not demand elevated presence.
Assessment
This skill appears coherent and matches its description: it analyzes schemas and architecture documents to recommend encodings and a schema-evolution plan. Because it is instruction-only, it won't install software or ask for credentials. However, when using it: (1) only provide the schema/code/architecture files needed for the analysis — avoid pasting secrets, private keys, or unrelated config; (2) expect the agent to read any files you give it (Read) and to produce files or edits if you allow Write; and (3) follow recommended CI tooling (buf, protoc, avro-tools, schema registry) in a controlled environment before applying schema changes in production. If you need the agent to analyze a codebase, consider creating a minimized export that contains only schema and API-relevant files.Like a lobster shell, security has layers — review code before you run it.
avrovk97ek9nn216mtbetr8pcjyygk984m4xjbackward-compatibilityvk97ek9nn216mtbetr8pcjyygk984m4xjbinary-encodingvk97ek9nn216mtbetr8pcjyygk984m4xjbookforgevk97ek9nn216mtbetr8pcjyygk984m4xjdataflowvk97ek9nn216mtbetr8pcjyygk984m4xjencodingvk97ek9nn216mtbetr8pcjyygk984m4xjevolvabilityvk97ek9nn216mtbetr8pcjyygk984m4xjforward-compatibilityvk97ek9nn216mtbetr8pcjyygk984m4xjgrpcvk97ek9nn216mtbetr8pcjyygk984m4xjjsonvk97ek9nn216mtbetr8pcjyygk984m4xjlatestvk97ek9nn216mtbetr8pcjyygk984m4xjmessage-brokervk97ek9nn216mtbetr8pcjyygk984m4xjprotobufvk97ek9nn216mtbetr8pcjyygk984m4xjrolling-upgradevk97ek9nn216mtbetr8pcjyygk984m4xjrpcvk97ek9nn216mtbetr8pcjyygk984m4xjschema-evolutionvk97ek9nn216mtbetr8pcjyygk984m4xjschema-registryvk97ek9nn216mtbetr8pcjyygk984m4xjserializationvk97ek9nn216mtbetr8pcjyygk984m4xjthriftvk97ek9nn216mtbetr8pcjyygk984m4xjxmlvk97ek9nn216mtbetr8pcjyygk984m4xj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis