Real Skill packageSource verifiedClawHub registry

ViBo SelfDeed

Use when the owner hands the agent a multi-step task: grill the intent first (G1-G5 plan card, owner gate), then run it as an autonomous mission — restore context from ViBo memory, find and fix problems safely, iterate via paths A/B/C, save lessons. Optional Telegram notify/ask/report (OFF by default, runtime-warned; sends mission data only when the owner sets TELEGRAM_MISSION_TOKEN/CHAT). Built-in DEMO memory (100 facts) works without the ViBo CLI. Use ONLY with the user's explicit consent: missions save progress…

Identity and source

Publisher attributionViBoregistry owner unverified by skillvetai
Functional categoryAgent Engineering, Security & Governanceautomatically inferred · 61% rule confidence
Package forminstruction with code12 recorded files
Canonical sourceClawHub registryclawhub:vnbochkarev-netizen:vibo-selfdeed
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 8/31/2026.claude/skills/vibo-selfdeed

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 8/31/2026.agents/skills/vibo-selfdeed

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 8/31/2026skills/vibo-selfdeed

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @vnbochkarev-netizen/vibo-selfdeed
clawhub inspect @vnbochkarev-netizen/vibo-selfdeed --version 1.0.13

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
12 / 12 inspected as text
Checked
8/31/2026, 12:46:38 PM
Scanner
0.1.3
Policy
1.0.3
5 inferred permission indicators
  • shell execution — automatically inferred
  • network access — automatically inferred
  • filesystem read — automatically inferred
  • filesystem write — automatically inferred
  • credential access — automatically inferred
3 dependency and API indicators
  • api: api.telegram.org
  • api: clawhub.ai
  • api: wwwvibo.com
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
8/31/2026, 7:03:55 AM
Release binding
Matches this record
  • vt: clean
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:f3dba1ef5406ef5ef0eca76278147e0eb0523c73f388fec6519e0421176c18d5
Show up to 12 recorded paths
  • EULA.md
  • examples/README.md
  • INSTALL.md
  • lib_vibo.py
  • package.json
  • README.md
  • run_mission.sh
  • safety.py
  • skill-card.md
  • SKILL.md
  • TASK.md
  • telegram_mission.py

Source changelog

Subagent check: notify/ask now print stderr warning when Telegram not configured (1.0.12 guard only covered _api; off-branch missed it)

Release security diff

mediumCompared fixed releases 1.0.11 and 1.0.13; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.118/29/2026sha256:99046a54c2c12cd715e7b0bac5c2f9859b1b4eaa3f89202a3b1cb3fcada05009
1.0.108/20/2026sha256:e5bd3942feed9f5cba220393d4a2a4c1110c2b695f511cddcf46cf1336d7e50e
1.0.88/16/2026sha256:b3ee10ebc2c8a08b42ae3c0946ae6b44b5fe94747aa9e6826c7bd66c35a827ca
1.0.08/16/2026sha256:3b8e93c4d900539227bfb96dc244cb4353c23a921491da56a66f4335841d6bb0