{"id":"f9cb61d2-a522-4bdb-b815-3c5393b9f516","entityType":"agent","slug":"clawhub-bqw1013-websculpt","name":"WebSculpt: Browser Automation with Memory","canonicalUrl":"https://www.xpersona.co/agent/clawhub-bqw1013-websculpt","canonicalPath":"/agent/clawhub-bqw1013-websculpt","generatedAt":"2026-10-10T14:45:34.407Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":null},"description":"Browser automation solution with CLI memory layer for high-speed, stable browser access. Usage examples: To download a video, send \"/websculpt-explore Use my browser to download this video for me.\" If the command stops working due to a website redesign, send \"/websculpt-maintain The YouTube video Skill: WebSculpt: Browser Automation with Memory Owner: bqw1013 Summary: Browser automation solution with CLI memory layer for high-speed, stable browser access. Usage examples: To download a video, send \"/websculpt-explore Use my browser to download this video for me.\" If the command stops working due to a website redesign, send \"/websculpt-maintain The YouTube video Tags: latest:1.0.13 Version history: v1.0.13 | 20","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s179y0ndmk9g4e5zv1rbg9qha58are6r:websculpt","sourceUrl":"https://clawhub.ai/bqw1013/websculpt","homepage":"https://clawhub.ai/bqw1013/skills/websculpt","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/bqw1013/websculpt","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/bqw1013/skills/websculpt","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":63,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Browser automation solution with CLI memory layer for high-speed, stable browser access. Usage examples: To download a video, send \"/websculpt-explore Use my br"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":null},"stars":null,"forks":null,"downloads":1431,"packageName":null,"latestVersion":"1.0.13","tractionLabel":"1.4K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T12:33:05.437Z","lastCrawledAt":"2026-10-10T12:33:05.437Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T12:33:05.437Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.13","createdAt":"2026-08-07T17:23:21.929Z","changelog":"websculpt 1.0.13 - Removed the sample file skill-card.md. - No changes to user-facing features or documentation.","fileCount":3,"zipByteSize":5315},{"version":"1.0.12","createdAt":"2026-08-03T13:59:31.388Z","changelog":"- Removed redundant documentation file skill-card.md for a cleaner skill package. - No changes to core functionality or protocols; all usage instructions and setup remain unchanged. - This update is maintenance-focused, reducing duplicated or unnecessary files.","fileCount":3,"zipByteSize":5255},{"version":"1.0.11","createdAt":"2026-08-02T13:13:58.518Z","changelog":"- Removed the sample file skill-card.md from the project. - No functional or user-facing changes; this update is a cleanup of unused documentation.","fileCount":3,"zipByteSize":5226},{"version":"1.0.10","createdAt":"2026-07-31T17:32:05.156Z","changelog":"- Removed the file: skill-card.md - No changes made to feature logic or usage instructions - Documentation structure and core guidance remain unchanged","fileCount":3,"zipByteSize":5250},{"version":"1.0.9","createdAt":"2026-07-30T16:04:22.576Z","changelog":"websculpt 1.0.9 - Removed the file skill-card.md from the project. - No changes made to core functionality or setup instructions.","fileCount":3,"zipByteSize":5233},{"version":"1.0.8","createdAt":"2026-07-29T15:56:01.705Z","changelog":"WebSculpt 1.0.8 - Removed the sample skill card file (`skill-card.md`) for cleanup and redundancy reduction. - No changes to the bootstrap process or user-facing functionality. - Maintains full guidance for installation, environment probing, and routing to lifecycle skills.","fileCount":3,"zipByteSize":5375},{"version":"1.0.7","createdAt":"2026-07-28T10:13:14.819Z","changelog":"websculpt 1.0.7 - Removed the sample skill-card.md file for a cleaner package. - No user-facing or functional changes; all usage and setup instructions remain unchanged.","fileCount":3,"zipByteSize":5341},{"version":"1.0.6","createdAt":"2026-07-27T04:34:08.419Z","changelog":"websculpt 1.0.6 - Removed the file `skill-card.md` from the project. - No changes were made to the core logic or workflow. - Documentation and usage instructions remain unchanged.","fileCount":3,"zipByteSize":5347}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s179y0ndmk9g4e5zv1rbg9qha58are6r:websculpt","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T14:45:34.401Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bqw1013-websculpt/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":null},"readme":"Skill: WebSculpt: Browser Automation with Memory\n\nOwner: bqw1013\n\nSummary: Browser automation solution with CLI memory layer for high-speed, stable browser access.\nUsage examples: \nTo download a video, send \"/websculpt-explore Use my browser to download this video for me.\" \nIf the command stops working due to a website redesign, send \"/websculpt-maintain The YouTube video\n\nTags: latest:1.0.13\n\nVersion history:\n\nv1.0.13 | 2026-08-07T17:23:21.929Z | user\n\nwebsculpt 1.0.13\n\n- Removed the sample file skill-card.md.\n- No changes to user-facing features or documentation.\n\nv1.0.12 | 2026-08-03T13:59:31.388Z | user\n\n- Removed redundant documentation file skill-card.md for a cleaner skill package.\n- No changes to core functionality or protocols; all usage instructions and setup remain unchanged.\n- This update is maintenance-focused, reducing duplicated or unnecessary files.\n\nv1.0.11 | 2026-08-02T13:13:58.518Z | user\n\n- Removed the sample file skill-card.md from the project.\n- No functional or user-facing changes; this update is a cleanup of unused documentation.\n\nv1.0.10 | 2026-07-31T17:32:05.156Z | user\n\n- Removed the file: skill-card.md\n- No changes made to feature logic or usage instructions\n- Documentation structure and core guidance remain unchanged\n\nv1.0.9 | 2026-07-30T16:04:22.576Z | user\n\nwebsculpt 1.0.9\n\n- Removed the file skill-card.md from the project.\n- No changes made to core functionality or setup instructions.\n\nv1.0.8 | 2026-07-29T15:56:01.705Z | user\n\nWebSculpt 1.0.8\n\n- Removed the sample skill card file (`skill-card.md`) for cleanup and redundancy reduction.\n- No changes to the bootstrap process or user-facing functionality.\n- Maintains full guidance for installation, environment probing, and routing to lifecycle skills.\n\nv1.0.7 | 2026-07-28T10:13:14.819Z | user\n\nwebsculpt 1.0.7\n\n- Removed the sample skill-card.md file for a cleaner package.\n- No user-facing or functional changes; all usage and setup instructions remain unchanged.\n\nv1.0.6 | 2026-07-27T04:34:08.419Z | user\n\nwebsculpt 1.0.6\n\n- Removed the file `skill-card.md` from the project.\n- No changes were made to the core logic or workflow.\n- Documentation and usage instructions remain unchanged.\n\nv1.0.5 | 2026-07-25T06:25:22.754Z | user\n\nWebSculpt 1.0.5\n\n- Removed the redundant skill-card.md file for better maintainability and clarity.\n- No changes to functionality or usage instructions.\n\nv1.0.4 | 2026-07-23T05:20:19.708Z | user\n\nwebsculpt 1.0.4\n\n- Removed the sample file `skill-card.md`.\n- No changes to functionality or user-facing documentation.\n\nv1.0.3 | 2026-07-22T10:14:36.213Z | user\n\nWebSculpt 1.0.3\n\n- Removed the sample file skill-card.md.\n- No user-facing changes to functionality or documentation.\n\nv1.0.2 | 2026-07-21T14:16:48.668Z | user\n\n- Removed the redundant skill-card.md file.\n- No changes to code or functionality.\n- Documentation and usage remain unchanged.\n\nv1.0.1 | 2026-07-21T07:30:09.608Z | user\n\nwebsculpt 1.0.1\n\n- Updated example scenarios and platform references (e.g., replaced Douyin, Xiaohongshu, Bilibili, and Zhihu with TikTok, YouTube, Instagram, Reddit, and X) for broader international relevance.\n- Modernized sample commands in usage documentation.\n- Removed the obsolete skill-card.md file for cleaner repository maintenance.\n\nv1.0.0 | 2026-07-21T06:19:32.813Z | auto\n\nWebSculpt 1.0.0 initial release\n\n- Provides setup and bootstrap entry point for installing and configuring the WebSculpt CLI and its lifecycle skills.\n- Guides probing the environment and managing installation, updates, or repairs for WebSculpt and its dependencies.\n- Ensures correct installation of Node.js, WebSculpt CLI, and @playwright/cli.\n- Describes a four-stage command lifecycle: exploration, capture, maintenance, and library management, each handled by a corresponding skill.\n- Clarifies when to activate, route, or stay dormant, depending on system readiness and user intent.\n\nArchive index:\n\nArchive v1.0.13: 3 files, 5315 bytes\n\nFiles: skill-card.md (2070b), SKILL.md (9367b), _meta.json (129b)\n\nFile v1.0.13:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.13:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.13\",\n \"publishedAt\": 1786123401929\n}\n\nFile v1.0.13:skill-card.md\n\n## Description:\n\nWebSculpt bootstraps a CLI-backed browser automation workflow for acquiring external information, scraping pages, calling APIs, and maintaining reusable web operation commands.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[bqw1013](https://clawhub.ai/user/bqw1013)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, researchers, content teams, ecommerce operators, and analysts use WebSculpt to install and route browser automation workflows that access web information behind login or content walls and convert repeated web operations into reusable CLI commands.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill installs or updates the global WebSculpt package and persistent agent skills.\n\nMitigation: Install only if the WebSculpt package is trusted, prefer a project-local install where practical, pin and review the exact WebSculpt version, and inspect generated lifecycle skill files before allowing automatic use.\n\nRisk: Browser automation may run on machines with logged-in browser sessions or sensitive data.\n\nMitigation: Use a constrained browser profile or isolated environment, review commands before execution, and avoid granting access to accounts or data beyond the intended task.\n\n## Reference(s):\n\n- [WebSculpt Skill on ClawHub](https://clawhub.ai/bqw1013/skills/websculpt)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May direct the agent to install or update WebSculpt, Playwright CLI, and lifecycle skills before routing the user's web automation task.]\n\n## Skill Version(s):\n\n1.0.13 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.12: 3 files, 5255 bytes\n\nFiles: skill-card.md (1983b), SKILL.md (9367b), _meta.json (129b)\n\nFile v1.0.12:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.12:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.12\",\n \"publishedAt\": 1785765571388\n}\n\nFile v1.0.12:skill-card.md\n\n## Description:
\nWebSculpt bootstraps browser automation tooling and lifecycle skills for agents that need to gather web information, scrape pages, call APIs, or build reusable browser commands.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and agent users use WebSculpt to install or repair WebSculpt, verify browser automation readiness, and route web acquisition tasks into its explore, capture, maintain, and library lifecycle skills.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can add or update global agent skills and browser automation tooling across home-directory skill locations.
\nMitigation: Install only when WebSculpt setup or repair is intended, and prefer a project-local install while testing.
\nRisk: Later lifecycle skills may operate browser automation against authenticated web sessions.
\nMitigation: Use caution with logged-in browser profiles and accounts, and review planned browser actions before allowing them to run.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline bash code blocks]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Provides setup, status-check, repair, and routing guidance for browser automation workflows.]
\n\n## Skill Version(s):
\n1.0.12 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.11: 3 files, 5226 bytes\n\nFiles: skill-card.md (1976b), SKILL.md (9367b), _meta.json (129b)\n\nFile v1.0.11:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.11:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.11\",\n \"publishedAt\": 1785676438518\n}\n\nFile v1.0.11:skill-card.md\n\n## Description:
\nWebSculpt bootstraps browser automation with a reusable command library by installing or repairing its CLI and lifecycle skills for external information gathering, scraping, API calls, and browser tasks.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this skill to set up WebSculpt, then route browser automation and repeatable web information workflows into the appropriate WebSculpt lifecycle skill.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The security review flags persistent global installs that can affect future agent sessions.
\nMitigation: Prefer project-local installation when possible and ask the agent to report exact install paths and package versions before making changes.
\nRisk: The skill can add global npm tooling and lifecycle skills under home-directory agent skill folders.
\nMitigation: Review requested install scope before execution and verify WebSculpt status after installation.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, configuration]
\n**Output Format:** [Markdown with inline shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May install global npm tooling and persistent lifecycle skills when the environment is not already configured.]
\n\n## Skill Version(s):
\n1.0.11 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.10: 3 files, 5250 bytes\n\nFiles: skill-card.md (1957b), SKILL.md (9367b), _meta.json (129b)\n\nFile v1.0.10:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.10:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.10\",\n \"publishedAt\": 1785519125156\n}\n\nFile v1.0.10:skill-card.md\n\n## Description:
\nWebSculpt bootstraps and repairs a browser automation CLI and lifecycle skill set for acquiring web information and turning repeated browser workflows into reusable commands.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and external users use this skill to install, verify, update, or repair WebSculpt before using browser automation for information acquisition, scraping, API work, or reusable command-library workflows.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The setup flow can install global tools and persistent agent skills across the user's home directory without a separate approval step.
\nMitigation: Confirm the install scope, npm packages, and target skill directories before running install commands; use a project-local install when global availability is not needed.
\nRisk: Browser automation in logged-in sessions or on third-party sites can expose account data or perform actions as the user.
\nMitigation: Use least-privilege browser sessions, review target sites and actions before execution, and avoid sensitive accounts unless they are required for the task.
\n\n\n## Reference(s):
\n\n\n## Skill Output:
\n**Output Type(s):** [text, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [None]
\n\n## Skill Version(s):
\n1.0.10 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.9: 3 files, 5233 bytes\n\nFiles: skill-card.md (1957b), SKILL.md (9367b), _meta.json (128b)\n\nFile v1.0.9:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.9:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.9\",\n \"publishedAt\": 1785427462576\n}\n\nFile v1.0.9:skill-card.md\n\n## Description:
\nWebSculpt is a bootstrap skill that installs or repairs the WebSculpt CLI and routes browser automation, scraping, API, external-information, and reusable command-library tasks to its lifecycle skills.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this bootstrap skill to prepare WebSculpt in an agent environment, then route web acquisition, browser automation, command capture, maintenance, and command-library management tasks to the installed lifecycle skills.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill defaults to broad global npm package installation and global agent-skill changes across multiple agent environments.
\nMitigation: Review before installing, prefer a project-local install unless global availability is intended, and confirm the scope before running install or update commands.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline bash code blocks and concise routing guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May direct the agent to run environment probes, npm install or update commands, skill status checks, and follow-up routing steps.]
\n\n## Skill Version(s):
\n1.0.9 (source: server release metadata and user changelog)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.8: 3 files, 5375 bytes\n\nFiles: skill-card.md (2373b), SKILL.md (9367b), _meta.json (128b)\n\nFile v1.0.8:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.8:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.8\",\n \"publishedAt\": 1785340561705\n}\n\nFile v1.0.8:skill-card.md\n\n## Description:
\nWebSculpt bootstraps the WebSculpt CLI and lifecycle skills for browser automation, external information acquisition, API calls, and reusable command-library workflows.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, researchers, content teams, e-commerce operators, finance professionals, and consultants use this skill to install or repair WebSculpt and route browser automation tasks to its lifecycle skills. It supports workflows that acquire information from web pages, logged-in contexts, content walls, APIs, and repeated web operations that can become reusable commands.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can add global npm tooling and persistent lifecycle skills that future agent sessions may use automatically.
\nMitigation: Install only when that persistent automation behavior is intended, prefer project-local installation where practical, and review installed lifecycle skill files before use.
\nRisk: Browser automation may interact with logged-in accounts, private data, or high-impact web actions.
\nMitigation: Use reviewed commands and explicit user approval before running workflows that access sensitive sessions, private data, purchases, account changes, or other consequential actions.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and configuration guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May install global or project-local WebSculpt CLI tooling and persistent lifecycle skills when the environment probe indicates installation or repair is needed.]
\n\n## Skill Version(s):
\n1.0.8 (source: server evidence release.version)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.7: 3 files, 5341 bytes\n\nFiles: skill-card.md (2250b), SKILL.md (9367b), _meta.json (128b)\n\nFile v1.0.7:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.7:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1785233594819\n}\n\nFile v1.0.7:skill-card.md\n\n## Description:
\nWebSculpt bootstraps a browser automation CLI and lifecycle skills for acquiring web information, scraping pages, calling APIs, and creating reusable command workflows.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this skill to install or verify WebSculpt, then route browser automation, scraping, API-calling, command capture, repair, and library-management tasks to the appropriate lifecycle skill.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can install global npm packages and persistent agent skills.
\nMitigation: Probe the environment before installing, prefer project-local installation when possible, and confirm the npm package and version before global installs.
\nRisk: Browser automation may use logged-in sessions or access content behind account walls.
\nMitigation: Use browser sessions intentionally, avoid exposing sensitive account data, and review retrieved information before relying on it.
\nRisk: Exported command packages may contain sensitive evidence from prior automation runs.
\nMitigation: Review and redact exported command packages before sharing, migrating, or storing them outside the project.
\n\n\n## Reference(s):
\n- [WebSculpt ClawHub listing](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [Shell commands, Configuration instructions, Guidance]
\n**Output Format:** [Markdown with inline bash code blocks]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May install persistent lifecycle skills and route follow-on tasks to WebSculpt exploration, capture, maintenance, or library workflows.]
\n\n## Skill Version(s):
\n1.0.7 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.6: 3 files, 5347 bytes\n\nFiles: skill-card.md (2341b), SKILL.md (9367b), _meta.json (128b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1785126848419\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:
\nWebSculpt bootstraps a CLI-backed browser automation workflow for external information acquisition, page scraping, API calls, and reusable browser command memory.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users, developers, and agents use this skill to install or recover WebSculpt, then route work into lifecycle skills for browser automation, web data acquisition, scraping, API calls, and repeated web operations.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may install global npm packages and persistent lifecycle skills under the user's home directory.
\nMitigation: Review the install scope before use and prefer project-local installation when persistent global behavior is not desired.
\nRisk: The skill can route agents toward browser automation involving logged-in websites or private account data.
\nMitigation: Use it only with accounts and sessions approved for automation, and review outputs before relying on or sharing collected data.
\nRisk: The security verdict is suspicious because the bootstrap workflow can change future agent behavior through installed lifecycle skills.
\nMitigation: Review and scan the installed lifecycle skills before deployment, especially in shared or production agent environments.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and routing guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May direct the agent to install or verify WebSculpt CLI tooling and lifecycle skills before routing browser automation work.]
\n\n## Skill Version(s):
\n1.0.6 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.5: 3 files, 5406 bytes\n\nFiles: skill-card.md (2435b), SKILL.md (9367b), _meta.json (128b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1784960722754\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:
\nWebSculpt bootstraps browser automation with a reusable command library by installing or repairing the WebSculpt CLI and routing agents to lifecycle skills for exploration, capture, maintenance, and library management.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, researchers, analysts, content operators, and ecommerce teams use this skill to set up WebSculpt when they need browser automation, web data acquisition, API calls, scraping, or reusable commands for repeated web workflows.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can install persistent global tooling and lifecycle skills across multiple agent skill directories.
\nMitigation: Install only when persistent WebSculpt behavior is desired, and prefer project-local installation when the workflow should stay scoped to one project.
\nRisk: The default global setup can modify skill directories under the user's home folder.
\nMitigation: Review the installation scope and installed files before allowing global setup or later updates.
\nRisk: Browser automation and scraping workflows may access logged-in or content-gated web data.
\nMitigation: Use WebSculpt only for accounts, sites, and data sources the user is authorized to access, and review generated commands before reuse.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/bqw1013/skills/websculpt)
\n- [Skill documentation](artifact/SKILL.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and routing instructions.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May install persistent global or project-local WebSculpt tooling and lifecycle skill files depending on user intent and environment state.]
\n\n## Skill Version(s):
\n1.0.5 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.4: 3 files, 5335 bytes\n\nFiles: skill-card.md (2252b), SKILL.md (9367b), _meta.json (128b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain**: when an installed command breaks, errors out, or needs new parameters or output changes, use it to repair. For example:\n\n ```\n /websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10\n ```\n\n- **websculpt-library**: when there are too many commands and you want to narrow the display, or you need to back up, migrate, or share the command library. For example:\n\n ```\n /websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up\n ```\n\n## Role\n\nThis skill is the WebSculpt bootstrapper, not an information-gathering tool. It plays three time-phased roles:\n\n1. **Installer** (first trigger): check the environment, install the WebSculpt CLI and the four lifecycle skills (explore / capture / maintain / library).\n2. **Stand-in router** (remainder of the installing session): newly installed skills are not yet in the host's skill listing. You must read the corresponding installed skill file and follow its protocol to continue the user's task.\n3. **Dormant recovery entry** (all later sessions): this skill should not trigger anymore — the lifecycle skills are in place. It wakes only when WebSculpt is broken (e.g. `websculpt: command not found`) or the user explicitly asks to install / update / repair it.\n\n## Step 1: Probe\n\nAlways probe before acting; never install blindly:\n\n```bash\nwebsculpt --version\n```\n\n- Command not found → proceed to \"Install\".\n- Command works → run `websculpt skill status`. This command has no exit-code semantics — judge by its output text: each skill line reports `installed local`, `installed global`, or `not installed`.\n - All four lifecycle skills report `installed local` or `installed global`, and the user has no install / update / repair intent → go straight to \"Route\"; do not reinstall.\n - Any skill reports `not installed` → run `npm install -g @playwright/cli@0.1.13` and step 3 of \"Install\" (install the lifecycle skills), then go to \"Route\".\n- The user explicitly asks to update / repair → go to \"Update and Repair\".\n\n## Install\n\n### 1. Check Node.js\n\n```bash\nnode --version\n```\n\nNode.js >= 22 is required. If not met, tell the user to install Node.js 22 or later and stop.\n\n### 2. Install the CLI and the browser tool\n\n```bash\nnpm install -g @playwright/cli@0.1.13 websculpt\n```\n\n`@playwright/cli` is the browser-automation dependency used during explore; install it together with the CLI.\n\nIf the global install fails due to permissions (e.g. EACCES), do not use sudo — sudo does not exist on Windows, and a sudo install leaves root-owned files in the npm global directory, breaking every later npm operation with permission errors. Use the npx fallback instead: prefix every subsequent `websculpt` command with `npx -y websculpt@latest` and every `playwright-cli` command with `npx -y @playwright/cli@0.1.13` (including skill install and status below).\n\n### 3. Install the lifecycle skills\n\n```bash\nwebsculpt skill install --global\n```\n\nThis command is idempotent; existing skills are skipped. A global install writes to `.claude/skills/`, `.codex/skills/`, and `.agents/skills/` under the user's home directory — the host agent only needs to read one of them.\n\n`--global` is the default here. If the user explicitly wants WebSculpt only inside one project, run `websculpt skill install` (without `--global`) in that project's root instead, which requires an existing `.claude/`, `.codex/`, or `.agents/` directory there.\n\n### 4. Verify and report\n\n```bash\nwebsculpt skill status\n```\n\nConfirm all four lifecycle skills report `installed local` or `installed global`. Briefly report to the user: the CLI version, the skill install locations (scope and directories), and that future sessions will trigger these skills automatically.\n\n## Route\n\nOnce installation is done (or the probe found everything ready), continue the user's original task:\n\n1. Identify the task's stage: acquiring external information → `websculpt-explore`; solidifying a validated path into a command → `websculpt-capture`; fixing or iterating a broken command → `websculpt-maintain`; organizing / migrating the command library → `websculpt-library`. Most tasks start with explore.\n2. Read the corresponding installed skill file and strictly follow its protocol. Locate it by the scope reported by `skill status`: `installed global` means `.agents/skills//SKILL.md` under the user's home directory (identical copies exist under `.claude/skills/` and `.codex/skills/`); `installed local` means the same path under the current project directory.\n3. Within this session, whenever any websculpt skill's protocol calls for loading another websculpt skill (e.g. explore suggesting capture), likewise read that skill's installed SKILL.md file instead of relying on host triggering.\n4. Do not ask the user to restart the session or restate the task; take over yourself.\n\n## Update and Repair\n\n- Update: `npm update -g websculpt`, then `websculpt skill install --global --force` to refresh the skills so they stay in sync with the new CLI version.\n- Repair: if the `websculpt` command is missing or broken, re-run the \"Install\" flow.\n- If `skill install` / `skill status` fails with an unknown command or option, the CLI is outdated: run `npm update -g websculpt` first and retry.\n- A broken individual command (a `domain/action`) is not this skill's responsibility; route it to websculpt-maintain.\n\n## Prohibited\n\n- Do not run any install command before probing (`websculpt --version` / `websculpt skill status`).\n- Do not reinstall when the CLI and skills are already healthy, and do not ask the user to restart the session; route and continue the task directly.\n- Do not use sudo to work around npm global install permission errors; use the npx fallback instead.\n- Do not hand-edit the four installed lifecycle skill files; they are refreshed exclusively via `websculpt skill install --force`.\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1784784019708\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nWebSculpt bootstraps the WebSculpt CLI and lifecycle skills for browser automation, authenticated information gathering, scraping, API calls, and reusable web command workflows.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[bqw1013](https://clawhub.ai/user/bqw1013)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, researchers, analysts, and operators use this skill to install or verify WebSculpt and route browser automation tasks to lifecycle skills for exploration, capture, maintenance, and library management.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The installer can persist WebSculpt skills globally across Claude, Codex, and other agent environments.
\nMitigation: Use project-local installation when broad persistence is not desired, and review the reported install locations after setup.
\nRisk: Logged-in browser automation can access accounts, sites, or data beyond the user's intended scope.
\nMitigation: Use WebSculpt only for accounts, sites, and data collection the user is authorized to access, and confirm task scope before automation.
\nRisk: The WebSculpt npm package and later lifecycle skills are external to this artifact.
\nMitigation: Review the installed package version and lifecycle skill files before relying on them for sensitive workflows.
\n\n\n## Reference(s):
\n- [ClawHub skill listing](https://clawhub.ai/bqw1013/skills/websculpt)
\n\n\n## Skill Output:
\n**Output Type(s):** [Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown instructions with bash command blocks]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May install global or project-local lifecycle skills and route subsequent tasks after setup.]
\n\n## Skill Version(s):
\n1.0.4 (source: ClawHub release evidence and user changelog)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: WebSculpt: Browser Automation with Memory Owner: bqw1013 Summary: Browser automation solution with CLI memory layer for high-speed, stable browser access. Usage examples: To download a video, send \"/websculpt-explore Use my browser to download this video for me.\" If the command stops working due to a website redesign, send \"/websculpt-maintain The YouTube video Tags: latest:1.0.13 Version history: v1.0.13 | 20","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"/websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio"},{"language":"text","snippet":"/websculpt-maintain The YouTube video download command stopped working — please fix it\n /websculpt-maintain The competitor price monitoring command has been returning empty data for days — take a look\n /websculpt-maintain Add a parameter to the X trending monitor so it only shows the top 10"},{"language":"text","snippet":"/websculpt-library Export the download commands for the various video platforms — I want to send them to a friend\n /websculpt-library There are too many commands — only show the e-commerce monitoring ones in this project\n /websculpt-library I switched to a new computer — import the command library I backed up"},{"language":"bash","snippet":"websculpt --version"},{"language":"bash","snippet":"node --version"},{"language":"bash","snippet":"npm install -g @playwright/cli@0.1.13 websculpt"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: websculpt\ndescription: Setup and bootstrap entry point for WebSculpt. Use when you need to acquire or verify external information, scrape web pages, call APIs, perform browser automation, or use the WebSculpt command library, and the websculpt command is unavailable (not installed or broken) in the current environment — you must complete setup through this skill before acquiring information. Also use when the user explicitly asks to install, update, or repair WebSculpt. If other WebSculpt lifecycle skills such as websculpt-explore are already present in your available skill list, the environment is ready — do not load this skill; use the corresponding lifecycle skill directly.\n---\n\n# WebSculpt Bootstrap\n\n## When to Use WebSculpt\n\nWebSculpt is good at two things: getting information from behind login walls and content walls, and turning high-frequency, repetitive web operations into CLI commands that you can later invoke in one sentence without re-spending model context. Typical scenarios:\n\n- **Content creators / self-media bloggers**: download video clips from TikTok, YouTube, or Instagram; analyze benchmark accounts' posting cadence and viral content; harvest comment-section feedback for topic ideas.\n- **E-commerce operators**: regularly monitor competitor stores' pricing, new listings, and sales changes; track competitor ad creatives.\n- **Investment research / finance professionals**: regularly pull research reports, filings, and high-frequency tracking data; quant teams can also harvest alternative data such as sentiment and community buzz.\n- **Consultants / industry researchers**: track industry developments — much first-hand information sits inside content platforms like Reddit and X.\n- **AI practitioners / researchers**: track AI products and competitor moves, follow frontier technology progress, and monitor community discussion heat.\n\nThese are only examples. Any scenario where \"the information is behind a wall\" or \"the operation repeats frequently\" is a good fit for WebSculpt.\n\n## The Four Lifecycle Skills\n\nA command's full lifecycle is: discover through exploration → solidify into a command → repair when broken → organize and migrate. Each stage is owned by one skill:\n\n- **websculpt-explore**: when the command library has no ready-made command for what you need, use it to explore and validate an acquisition path. Most tasks start here. For example:\n\n ```\n /websculpt-explore Use my browser to download the video at https://www.tiktok.com/@creator/video/1234567890\n /websculpt-explore Research Perplexity's feature updates over the past six months and organize them into a timeline\n /websculpt-explore Use my logged-in account to export this month's analytics report from YouTube Studio\n ```\n\n- **websculpt-capture**: once explore has proven a path end-to-end and you want to solidify it into a reusable command, use this. It is usually suggested by explore after validation passes; no manual triggering needed.\n\n- **websculpt-maintain"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7f8ggfyznfmj0r4rdsvg0c258ar8gv\",\n \"slug\": \"websculpt\",\n \"version\": \"1.0.13\",\n \"publishedAt\": 1786123401929\n}"},{"path":"skill-card.md","content":"## Description:\n\nWebSculpt bootstraps a CLI-backed browser automation workflow for acquiring external information, scraping pages, calling APIs, and maintaining reusable web operation commands.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[bqw1013](https://clawhub.ai/user/bqw1013)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, researchers, content teams, ecommerce operators, and analysts use WebSculpt to install and route browser automation workflows that access web information behind login or content walls and convert repeated web operations into reusable CLI commands.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill installs or updates the global WebSculpt package and persistent agent skills.\n\nMitigation: Install only if the WebSculpt package is trusted, prefer a project-local install where practical, pin and review the exact WebSculpt version, and inspect generated lifecycle skill files before allowing automatic use.\n\nRisk: Browser automation may run on machines with logged-in browser sessions or sensitive data.\n\nMitigation: Use a constrained browser profile or isolated environment, review commands before execution, and avoid granting access to accounts or data beyond the intended task.\n\n## Reference(s):\n\n- [WebSculpt Skill on ClawHub](https://clawhub.ai/bqw1013/skills/websculpt)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May direct the agent to install or update WebSculpt, Playwright CLI, and lifecycle skills before routing the user's web automation task.]\n\n## Skill Version(s):\n\n1.0.13 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Browser automation solution with CLI memory layer for high-speed, stable browser access. Usage examples: To download a video, send \"/websculpt-explore Use my browser to download this video for me.\" If the command stops working due to a website redesign, send \"/websculpt-maintain The YouTube video Skill: WebSculpt: Browser Automation with Memory Owner: bqw1013 Summary: Browser automation solution with CLI memory layer for high-speed, stable browser access. Usage examples: To download a video, send \"/websculpt-explore Use my browser to download this video for me.\" If the command stops working due to a website redesign, send \"/websculpt-maintain The YouTube video Tags: latest:1.0.13 Version history: v1.0.13 | 20","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1297,"uniquenessScore":47,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T12:33:05.437Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T14:45:34.407Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}