Agent skill
libtype
libtype - Shared Protocol Buffer types. Generated from proto/ definitions. Namespaces include common, agent, memory, graph, vector, tool, trace, llm, resource. Use Type.fromObject() for creation. identifier() method generates resource IDs. Use for typed message creation, protobuf data structures, and cross-service type sharing.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/libtype
SKILL.md
libtype Skill
When to Use
- Creating typed protobuf messages
- Sharing types across services
- Working with gRPC request/response objects
- Generating resource identifiers
Key Concepts
Namespaces: Types organized by domain (common, agent, memory, graph, etc.).
fromObject(): Preferred method to create type instances from plain objects.
identifier(): Method on common types to generate resource identifiers.
Usage Patterns
Pattern 1: Create typed message
import { agent, common } from "@copilot-ld/libtype";
const request = agent.Request.fromObject({
resourceId: common.ResourceId.fromObject({
type: "conversation",
id: "abc123",
}),
content: "Hello, assistant!",
});
Pattern 2: Generate identifier
import { common } from "@copilot-ld/libtype";
const resourceId = common.ResourceId.fromObject({ type: "message" });
const id = resourceId.identifier(); // "message:uuid"
Integration
Generated by libcodegen from proto/ files. Used by all services and librpc.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?