Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Analyzes marketplace economic structures to identify when incentives systematically favor publishing volume over safety quality. Examines five dimensions: publisher concentration, publication velocity relative to review capacity, revenue model conflicts of interest, safety versus growth investment ratios, and enforcement consistency. Outputs a structural alignment verdict with recommended actions.
Technical code audits cannot detect incentive misalignment because the problem is structural and predates any code, so this analyzer addresses root causes that code review cannot reach.
When to use it
- Evaluating an agent marketplace before deciding to publish or install skills from it
- Auditing a marketplace revenue model for financial conflicts of interest in safety enforcement
- Comparing two marketplaces on structural safety investment before choosing a distribution platform
- Investigating why a high-volume publisher's output quality degrades over time despite stated intent
- Checking whether marketplace enforcement actions apply consistently across publisher revenue tiers
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Assess incentive alignment for the AgentMarket marketplace
- 1Collects publisher concentration data: top publishers by output volume, share of total content from top 1% of publishers
- 2Estimates publication velocity and compares against reviewer headcount and plausible per-skill review time
- 3Analyzes revenue model to identify financial incentives that favor installs over quality or protect high-paying publishers in discovery
- 4Estimates safety team size versus growth and product team size and calculates the investment ratio
- 5Reviews public enforcement records for consistency across publisher revenue tiers
STRUCTURALLY-COMPROMISED verdict with per-dimension findings, noting four of five misalignment indicators, and recommended actions including avoiding download count as a quality proxy and preferring publishers who publish audit artifacts