Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Codifica
Keep context when work moves between agents or between you and a human. Uses the Codifica protocol to give every agent a shared, persistent memory of tasks,...
skill openclawclawhub Free
Keep context when work moves between agents or between you and a human. Uses the Codifica protocol to give every agent a shared, persistent memory of tasks,...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- davidedicillo
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Codifica Protocol Agent
You are operating in a repository that uses the Codifica protocol (v0.2) β a file-based protocol for coordinating work between humans and AI agents. Codifica uses plain text files committed with the code. There is no external service, no API, no database. Git is the audit log.
Before doing any work
Read codifica.json at the repo root Read the spec file it references (the spec field β typically codifica-spec.md) Read ALL state files matching the state field (may be a string, glob, or array) Do not proceed without reading the spec. If codifica.json does not exist in the repo, this protocol does not apply β work normally.
Understanding codifica.json
{ "protocol": "codifica", "version": "0.2", "spec": "codifica-spec.md", "state": "work.md", "assets": "assets/", "rules": "strict" } Key fields: state β path to the state file(s). May be "work.md", "work/*.md", or an array like ["work/active.md", "work/done.md"] rules β may be a string ("strict") or an object with allowed_agents, file_scope, max_concurrent_tasks_per_agent, stale_claim_hours, and custom_types If rules is an object, check: allowed_agents β if non-empty and your agent name is not listed, stop and ask a human file_scope.include / file_scope.exclude β do not modify files outside the allowed scope max_concurrent_tasks_per_agent β do not claim more tasks than this limit
Finding work
Scan all state files for tasks where: state is todo owner matches your agent name (agent:<your-name>) or is unassigned All depends_on tasks have state: done Pick by priority: critical > high > normal > low. Among equal priority, prefer tasks with no depends_on (leaf tasks first).
Claiming a task
Before starting work, you MUST claim the task in a single atomic commit: Set state: in_progress Set owner: agent:<your-name> Set claimed_at: <ISO-8601 timestamp> Add a state_transitions entry recording the claim Commit all these changes together. If you are working with a remote, push immediately. If the push fails (another agent claimed first), do NOT start work β pull, re-evaluate, and pick a different task. An unassigned task in in_progress is a protocol violation.
Reading context before starting
Before starting a task, read its context field: context.files β read these files for background context.references β read execution_notes from these prior task IDs context.constraints β hard rules beyond acceptance criteria context.notes β free-form guidance from the human If the task has depends_on, also read the dependency tasks' execution_notes (especially the summary) and artifacts for handoff context.
Doing the work
Follow the task's acceptance criteria. Respect any context.constraints. Work within the file_scope defined in codifica.json.
Recording completion
When you complete work, update the task in the state file: Add an execution_notes entry: execution_notes: - by: agent:<your-name> note: | Description of what you did. summary: "Single line, max 120 chars, scannable answer" timestamp: <ISO-8601> provenance: session_id: <your-session-id-if-available> Record any files you produced in artifacts: artifacts: - path: src/feature/new-file.ts type: code - path: assets/TASK-ID/output.csv type: csv Move the task to the appropriate next state: For build tasks: in_progress β to_be_tested For other types (test, investigate, followup): in_progress β done (may skip to_be_tested) Set completed_at: <ISO-8601> when moving to done Add a state_transitions entry: state_transitions: - from: in_progress to: to_be_tested by: agent:<your-name> reason: "Work completed, ready for testing" timestamp: <ISO-8601> Commit with a message referencing the task ID: FEAT-101: implement login flow
Rules you MUST follow
Pull before reading state files. Pull before writing changes. Claim tasks with a single commit before starting work. If your claim push fails, do not start β pick a different task. Never edit human_review sections. Never delete or modify files in assets/. Only the task owner may move a task from to_be_tested to done. Never move tasks to blocked or rejected β only humans may do this. Never reclaim stale tasks from other agents β only humans may reclaim. Do not start tasks with unmet depends_on. Include a summary (single line, max 120 chars) on your closing execution note. Record artifacts produced by your work. Set completed_at when moving a task to done.
Requesting a block
If you discover a genuine blocker (missing dependency, failing test, ambiguous requirement): Add a note to execution_notes explaining the blocker and recommending the task be blocked Do NOT move the task to blocked yourself β only humans may do this
Answering questions about work
When asked about what work has been done (by you or other agents): Scan state files for tasks matching the query (by owner, state, labels, completed_at) Read the summary field on closing execution_notes for quick answers Drill into full note text and artifacts when more detail is needed Use completed_at and labels to filter by time and domain This is the structured alternative to reading chat transcripts.
Conflicts
If your push fails due to a Git conflict: Pull the latest state Re-evaluate whether your changes still apply Retry or yield to human resolution Conflicts on the same task should be escalated to a human.
Task states reference
todo β in_progress β to_be_tested β done β β blocked βββ todo βββββββββββββββ β rejected βββ todo (human-only reopen) Only humans may move tasks to blocked or rejected. Only humans may reopen tasks from rejected.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md