Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Intent Align
Intent-alignment orchestration for OpenClaw agent teams across diverse host environments. Use when work must stay anchored to user goals while allowing flexi...
skill openclawclawhub Free
Intent-alignment orchestration for OpenClaw agent teams across diverse host environments. Use when work must stay anchored to user goals while allowing flexi...
β¬ 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, assets/mermaid-spec-template.md, references/core-contract.md, references/alignment-hub-template.md, references/adapters/adapter-template.md, references/adapters/local-repo.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
- 2.0.0
Provenance
- Publisher
- oscraters
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Intent-Align v2 Core
Keep execution aligned to user intent while preserving agent autonomy.
Quick Start
Read references/core-contract.md. Create alignment hub from references/alignment-hub-template.md. Run Intent Quality Gate before planning. Select adapters from references/adapters/. Execute phases with realignment and verification gates.
Workflow Contract
Build intent_snapshot and run intent_lint (see core contract). Ask for strictness mode and scope overrides (project/repo/workflow/task). Resolve effective strictness by precedence: task > workflow > repo > project > default. Evaluate ambiguity action using severity + strictness + risk class. Generate phase plan and Mermaid diagram with explicit dependencies and gates. Bind available adapters through capability_matrix. Execute phase-by-phase. Before phase start, run Pre-Execution Clarification Gate. On each phase end, run verification gates (including output conformance) and update drift evidence. If intent or constraints change, apply intent_delta and re-plan only impacted phases. Close with final alignment report and open ambiguity list (if any).
Autonomy Levels
1 Strict: Require user confirmation before each phase start. 2 Balanced: Require user confirmation at phase end or any critical drift. 3 Aggressive: Auto-continue on low drift; require confirmation on major deltas. 4 Exploratory: Continue with log-only check-ins unless risk or ambiguity threshold is exceeded. Override rule: high-risk ambiguity is never advisory-only; enforce at least soft_gate. Strictness rule: strictness mode controls whether ambiguities block or proceed with guardrails.
Required References
references/core-contract.md references/alignment-hub-template.md references/realignment-protocol.md references/verification-gates.md references/capability-taxonomy.md
Adapter Selection
Use only adapters needed for the task: references/adapters/github.md references/adapters/local-repo.md references/adapters/tracker-generic.md references/adapters/adapter-template.md If no adapter can satisfy a required capability: Generate an ad-hoc adapter spec from adapter-template.md. Add provenance metadata (created_by, created_at, environment_assumptions, tool_access_required). Validate required fields before use. Register the new adapter in capability_matrix.adapters_selected. Continue in degraded mode only if validation fails or auth/capability remains unavailable.
Anti-Bloat Rules
Keep core contract tool-agnostic. Do not add tracker- or host-specific logic to core files. Add a new adapter only for a proven capability gap. Keep schemas single-source; do not duplicate fields across files. Tie each new feature to one concrete failure mode and one test scenario. Generate ad-hoc adapters only for current task scope; do not pre-generate broad catalogs. Use canonical capability IDs first; extend only when needed via namespaced custom IDs.
Edge Cases
Multi-repo: maintain one hub with per-repo adapter bindings and dependency graph. Non-git prototype: use local artifacts and explicit acceptance criteria checkpoints. Team swarm: assign owner per phase and keep decision log in hub.
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
6 Docs
- SKILL.md
- assets/mermaid-spec-template.md
- references/adapters/adapter-template.md
- references/adapters/local-repo.md
- references/alignment-hub-template.md
- references/core-contract.md