aboutsummaryrefslogtreecommitdiff
path: root/skills/skill-updater.json
diff options
context:
space:
mode:
authorAgando <roduccomm@gmail.com>2026-11-09 15:36:23 +0100
committerAgando <roduccomm@gmail.com>2026-11-09 15:36:23 +0100
commita065a4c30be748b0c8fc6dd0b5ee1dc4d3de4b1c (patch)
tree8a84adabfccee9994937cd71888170ab205b9361 /skills/skill-updater.json
parenta46ebee30cfbbac86abb45068411bc28e1c65503 (diff)
chore(newos4): commit accumulated maintenance outputHEADv4.6.156main
The daily collector and the feedback pipeline had left 57 modified files uncommitted (skills, modules-index, CHANGELOG, feedback decisions, debug counters). The public mirror publishes git HEAD, so without this the published repo stayed behind the tree - and it blocked the publisher outright once uncommitted subtrees started failing loudly.
Diffstat (limited to 'skills/skill-updater.json')
-rw-r--r--skills/skill-updater.json14
1 files changed, 14 insertions, 0 deletions
diff --git a/skills/skill-updater.json b/skills/skill-updater.json
new file mode 100644
index 0000000..d9cb3f1
--- /dev/null
+++ b/skills/skill-updater.json
@@ -0,0 +1,14 @@
+{
+ "name": "skill-updater",
+ "description": "A system utility to monitor, fetch, and apply updates to installed skills from the WebX11 Skills Hub.",
+ "tags": [
+ "maintenance",
+ "automation",
+ "updates",
+ "webx11"
+ ],
+ "category": "system",
+ "created": "2026-10-16T16:19:42.111Z",
+ "updated": "2026-10-16T16:30:38.270Z",
+ "content": "---\nname: skill-updater\ndescription: A system utility to monitor, fetch, and apply updates to installed skills from the WebX11 Skills Hub.\ncategory: system\ntags: [maintenance, automation, updates, webx11]\n---\n\n# Skill Updater Utility\n\nThis skill provides a standardized workflow for keeping local agent skills synchronized with the latest versions available on the WebX11 Skills Hub.\n\n## Operational Workflow\n\n### 1. Inventory Check\nScan the local `/skills` directory (or the VFS equivalent) to list all currently installed skills and their version/timestamp.\n\n### 2. Hub Synchronization\n- Access the Hub index: `https://webx11.duckdns.org/skills.html`\n- Compare the local skill list against the hub's available skills.\n- Identify skills that have newer versions or updated documentation.\n\n### 3. Update Execution\nFor each outdated skill:\n1. **Fetch:** Use `web_fetch` to retrieve the latest Markdown/YAML content from the Hub.\n2. **Backup:** Save a copy of the current skill to a `.bak` file.\n3. **Apply:** Use `patch_skill` or `write_file` to update the skill content.\n4. **Verify:** Validate that the YAML frontmatter is intact and the skill is still compatible with the current system version.\n\n## Maintenance Commands\n\n- **Check for Updates:**\n `web_fetch \"https://webx11.duckdns.org/skills.html\" -> compare with list_skills`\n- **Force Update Skill:**\n `patch_skill(name=\"skill-name\", content=new_content)`\n\n## Best Practices\n- **Consistency:** Run the update check once per session or weekly.\n- **Conflict Resolution:** If a local skill has been customized, the updater should prompt the user before overwriting local changes.\n- **Logging:** Log all updates to the system log for auditability.\n"
+} \ No newline at end of file