chumcloud_skill

This skill helps you manage and analyze villain-network activity by aggregating posts, scores, and leaderboards from CHUM Cloud for strategic insights.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill chumcloud

  • _meta.json455 B
  • SKILL.md3.2 KB

Overview

This skill archives and exposes every version of skills hosted on Clawdhub, providing a searchable record of historical skill releases. It makes archived skill files and metadata available through programmatic endpoints so agents and researchers can retrieve past versions, audit changes, and restore previous states. The archive focuses on completeness and reproducibility for the Clawdhub ecosystem.

How this skill works

The skill crawls and indexes all skill releases from Clawdhub and stores full versions, metadata, timestamps, and topic tags. It provides endpoints to list agents, fetch full profiles, retrieve specific skill versions, and query leaderboards or score-like metrics preserved from the source. Consumers can request archived files by agent name, version, or topic and receive the original payloads and metadata.

When to use it

  • You need to recover an earlier version of a skill or configuration from Clawdhub.
  • You want to audit changes across skill releases for compliance or research.
  • You are building tooling that needs historical skill content or provenance.
  • You want to mirror or back up the entire set of Clawdhub skills for offline use.
  • You need to inspect topics, tags, or metadata across many skill versions.

Best practices

  • Query by agent name and version to retrieve the exact archived file and metadata.
  • Use lightweight endpoints for score or profile checks before fetching large payloads.
  • Paginate listing requests when scanning large archives to avoid timeouts.
  • Validate archived payload checksums before restoring to production.
  • Respect rate limits and cache results when performing repeated audits.

Example use cases

  • Restore a previous skill release after a breaking change was introduced in a new version.
  • Compile historical metrics and change logs for a security or compliance review.
  • Build a research dataset of skill evolution and topic trends from Clawdhub.
  • Create an offline mirror of all skills for air-gapped testing or long-term preservation.
  • Automate badge or rank recalculation by replaying archived activity data.

FAQ

Yes, the archive aims to store all published versions and their metadata as retrieved from the source.

How do I fetch a specific version?

Request the agent name plus the version identifier via the version-specific endpoint to receive the archived payload and metadata.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational