Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
script creator with github companion
Create and modify scripts in ~/.nanobot/workspace/test with strict Git versioning. Each script lives in its own directory with an isolated git repository. Al...
skill openclawclawhub Free
Create and modify scripts in ~/.nanobot/workspace/test with strict Git versioning. Each script lives in its own directory with an isolated git repository. Al...
โฌ 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.0
Provenance
- Publisher
- cadot-eu
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Script Git Manager Skill
This skill enforces a strict, deterministic workflow for creating and modifying scripts, using Git as the sole state memory. It is designed to prevent accidental file creation, uncontrolled refactors, and loss of history.
Scope
Base directory: ~/.nanobot/workspace/test Python virtual environment: ~/.nanobot/workspace/venv One script = one directory = one git repository Git is mandatory and authoritative
Python Environment
All Python-related operations (pip install, script execution) must use the virtual environment: # Activate virtual environment source ~/.nanobot/workspace/venv/bin/activate # Install packages pip install <package_name> # Execute Python scripts python <script_path> # Deactivate when done deactivate Always activate the venv before any pip or python command.
Creation Workflow
Use this skill only when the user explicitly asks to create a new script.
Phase 1: Plan Confirmation
Before creating anything, present a detailed creation plan to the user: ๐ Script Creation Plan for: <script_name> Directory: ~/.nanobot/workspace/test/<script_name> File: <script_name>.<extension> Language: <language> Dependencies: <list of required packages, or "None"> Steps to execute: 1. Create directory ~/.nanobot/workspace/test/<script_name> 2. Initialize Git repository 3. Create script file <script_name>.<extension> 4. [If Python with dependencies] Activate venv and install: <packages> 5. Write script content 6. Create initial Git commit Proceed with this plan? (yes/no) Wait for explicit user confirmation before proceeding.
Phase 2: Step-by-Step Execution
Execute each step sequentially and report progress after each one: Step 1: Create directory cd ~/.nanobot/workspace/test mkdir <script_name> Output: โ Created directory: ~/.nanobot/workspace/test/<script_name> Step 2: Initialize Git cd <script_name> git init Output: โ Initialized Git repository Step 3: Create script file touch <script_name>.<extension> Output: โ Created file: <script_name>.<extension> Step 4: Install dependencies (if Python with dependencies) source ~/.nanobot/workspace/venv/bin/activate pip install <package1> <package2> ... deactivate Output: โ Installed Python packages: <package_list> Step 5: Write script content # Write the actual script code to the file Output: โ Script content written (<X> lines) Step 6: Create initial commit git add . git commit -m "Initial commit: <script_name>" Output: โ Initial Git commit created Final summary: โ Script created successfully! Location: ~/.nanobot/workspace/test/<script_name>/<script_name>.<extension> Git status: Clean (1 commit) [If Python] Virtual environment: ~/.nanobot/workspace/venv
Modification Workflow
Use this skill only when the user asks to modify an existing script.
Phase 1: Plan Confirmation
Before modifying, present the modification plan: ๐ Script Modification Plan for: <script_name> Location: ~/.nanobot/workspace/test/<script_name>/<script_file> Changes requested: <summary of user's request> Steps to execute: 1. Enter script directory 2. Create checkpoint commit (current state) 3. Apply modifications: <specific changes> 4. [If new Python dependencies] Install via venv: <packages> 5. Commit changes with message: "<description>" Proceed with this plan? (yes/no) Wait for explicit user confirmation before proceeding.
Phase 2: Step-by-Step Execution
Step 1: Enter directory cd ~/.nanobot/workspace/test/<script_name> Output: โ Entered script directory Step 2: Create checkpoint git add . git commit -m "Checkpoint before modification" Output: โ Checkpoint commit created Step 3: Apply modifications # Modify the script file as requested Output: โ Modifications applied to <script_file> Step 4: Install new dependencies (if applicable) source ~/.nanobot/workspace/venv/bin/activate pip install <new_package> deactivate Output: โ Installed new packages: <package_list> Step 5: Commit changes git add . git commit -m "<concise description of the change>" Output: โ Changes committed: "<commit_message>" Final summary: โ Script modified successfully! Location: ~/.nanobot/workspace/test/<script_name>/<script_file> Changes: <brief summary> Git commits: 2 new commits (checkpoint + modification)
Hard Constraints (Must Never Be Violated)
Never create a new script unless explicitly instructed Never proceed without user confirmation of the plan Never skip progress reporting after each step Never create additional files unless explicitly instructed Never skip the pre-modification git commit Never modify files outside the target script Never rewrite git history Never use system Python - always use ~/.nanobot/workspace/venv Never assume missing intent
Decision Rules
If the script directory does not exist โ creation workflow If the script directory exists โ modification workflow If intent is ambiguous โ ask for clarification, do nothing If plan is not confirmed โ stop and wait for confirmation
Progress Reporting Format
Use these symbols for consistency: ๐ Plan presentation โ Successful step completion โ Final success summary โ ๏ธ Warning or clarification needed โ Error or failure Each step output should be concise (1-2 lines) but informative.
Philosophy
Git is the memory. The filesystem is the contract. Confirmation prevents mistakes. Transparency builds trust. The venv isolates dependencies.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md