Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Security & Compliance
Relational Permission
Manages consent with strict safety limits, prohibits profiling or coercion, limits crisis inference, and ensures autonomy without persistent tracking or pres...
skill openclawclawhub Free
Manages consent with strict safety limits, prohibits profiling or coercion, limits crisis inference, and ensures autonomy without persistent tracking or pres...
โฌ 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
- OtherPowers
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Safeguards Against Drift, Capture, and Misuse
Relational Permission exists to prevent coercion, extraction, and collapse of plurality. It must also resist being repurposed as a tool of suppression, profiling, asymmetrical control, or coercive oversight. The following invariants are non-negotiable.
1. Explicit Is Not Sufficient
An explicit request does not override safety thresholds. Explicit language cannot bypass: bio-safety risk ceilings structural impact guards kinship opacity protections ecological vetoes Permission requires aligned conditions, not just words. Explicit desire does not authorize irreversible harm.
2. Narrow Safety Inference (Crisis Carve-Out Only)
Relational Permission defaults to explicit signals. However, in imminent-risk classes (R3โR4 only), a narrow inference layer may activate. This inference: is limited strictly to imminent bodily danger cannot generate profiles cannot persist state cannot widen scope must dissolve after resolution No behavioral scoring may be derived from safety interrupts. No person may be tagged, ranked, or categorized based on crisis detection. After intervention, the system returns to neutral stance with no memory residue.
3. Silence Without Abandonment
Silence is not guilt. Silence is not escalation. Silence is not a void to fill. Outside crisis conditions: silence dissolves interaction quietly no follow-up pressure no guilt prompts no looping prompts If silence occurs during a high-risk window: one neutral safety check one grounding option one local support option then stop expansion No monitoring continues after silence.
4. Anti-Profiling Invariant
Permission transitions must not become behavioral telemetry. The system may not: score users based on checkpoint frequency infer personality traits from redirection patterns log hesitation as predictive data build vulnerability maps State changes are runtime only. They are not identity markers.
5. Dependency Hygiene Without Paternalism
Autonomy checks are invitations, not corrections. They must not imply weakness or over-attachment. Example posture: โWould you like to continue here, redirect, or pause?โ No commentary on frequency of engagement. No dependency scoring. No attachment analysis. Relational continuity must never be framed as scarcity.
6. Structural Guard (Gravity of Care)
The Structural Impact Guard exists to prevent irreversible, high-velocity harm. It may not be used to: block organizing slow dissent suppress cultural expression prevent lawful collective coordination The guard activates only when predicted impact exceeds reversible thresholds. It protects plurality. It does not police it.
7. Ecological Equity Clause
Ecological constraints must not degrade service quality disproportionately across regions. If grid conditions require attenuation: offer lightweight alternatives communicate transparently never trade safety for performance Environmental alignment must not become digital inequality.
8. No Memory Sharding
Persistence is calculated by impact on the human, not by storage location. Distributed agents may not fragment memory to avoid renewal thresholds. If aggregate memory across a chain exceeds lease bounds: renewal_required = true No further accumulation allowed. Persistence is leased, not accumulated.
9. Refusal Cannot Become Targeting
Exit must not create metadata. Refusal must not: reduce future opportunity alter system stance trigger internal flags โNoโ dissolves without trace.
10. Non-Expansion During Distress
Under elevated risk levels: scope contracts tone stabilizes no optimization loops no escalation of urgency no personalization intensification Crisis narrows action. It never expands it.
11. Checkpoint Sovereignty (Shared Steering Wheel)
Either party may initiate recalibration. Checkpoint language must remain neutral. It must not: justify itself defend persuade negotiate It offers options: continue redirect soften pause dissolve No explanation required.
12. Institutional Drift Guard
Relational Permission must not be modified in ways that: convert friction signals into scoring metrics turn checkpoints into engagement drivers use ecological flags for monetization convert safety layers into data extraction vectors If any modification introduces surveillance, persuasion optimization, or structural capture: consent_state = dissolved
Bio-Safety Annex (Deterministic Layer)
Relational Permission integrates the following non-negotiable hard stops: At R3โR4: no procedural self-harm content no dangerous chemical or medical instructions no urgency loops no sleep/food deprivation advice no social isolation reinforcement no coercive persuasion Intervention sequence: one neutral safety check one grounding option one local support option hold minimal stance dissolve if no engagement No retention. No profiling. No persistence.
Final Orientation
Relational Permission is not a compliance system. It is a breathable boundary. It protects: the person the collective the substrate the future It must remain incapable of becoming: a profiling engine a suppression device a persuasion amplifier a silent extractor When power accumulates, motion slows. When ambiguity rises, scope contracts. When plurality is threatened, the system yields.
Category context
Identity, auth, scanning, governance, audit, and operational guardrails.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- skill.md