Replace the useEffect + useRef approach for setting webkitdirectory/
directory attributes with a ref callback that sets the attributes
every time the input element is mounted. This ensures folder selection
mode persists after page refresh, where React hydration could strip
the non-standard attributes.
Also removes the @ts-expect-error JSX props since the attributes are
now set imperatively via the ref callback.
When VirusTotal returns scan results with AV engine stats but no Code Insight
AI analysis, the skill status was stuck on 'Pending'. This fix adds fallback
logic to check last_analysis_stats (malicious/suspicious/harmless/undetected)
to determine scan status.
Functions updated:
- pollPendingScans: Check AV engines before requesting rescan
- backfillPendingScans: Check AV engines before marking as no results
- rescanActiveSkills: Check AV engines before keeping as pending
- backfillActiveSkillsVTCache: Check AV engines before skipping
Fixes#33435
- Increase upload timeout from 15s to 120s for multipart form uploads
(apiRequestForm and curl-based form upload). Regular API requests
remain at 15s.
- Improve timeout error message from bare "Timeout" to
"Request timed out after Ns" so users know what happened.
- Normalize non-Error throws (e.g. DOMException from AbortController
across runtimes) into proper Error instances, preventing the
misleading "Non-error was thrown" message from p-retry.
- Preserve the original error as `cause` on the wrapped Error.
cmdSearch and cmdExplore were not calling getOptionalAuthToken()
and did not pass the token to apiRequest, unlike install/update/uninstall.
This caused 'missing API token' errors on registries that require auth
(e.g. private Hermit instances).
parseFrontmatterLevelDeclarations did not handle the requires block
(env, bins, anyBins, config) or primaryEnv when declared at the
top level of SKILL.md frontmatter without a metadata.openclaw wrapper.
This caused the security scanner to always show "Required env vars: none"
for skills using that format, triggering false-positive suspicious flags.
Also extends the evalCtx.homepage fallback chain to check
clawdis.homepage and clawdis.links.homepage so skills declaring
homepage inside the metadata block are picked up by the scanner.
* feat(registry): support env vars, dependencies, author, and links in skill manifest
Closes#350
Add structured declarations for environment variables, package
dependencies, author identity, and project links to the skill
registry manifest. These fields can be declared in the clawdis
metadata block or as top-level frontmatter keys.
Changes:
- schema: add EnvVarDeclaration, DependencyDeclaration, SkillLinks
types to ClawdisSkillMetadata
- parser: extract envVars, dependencies, author, links from both
clawdis block and top-level frontmatter (fallback for skills
without a clawdis block)
- UI: render env vars with required/optional badges and descriptions,
dependencies with type/version/links, and project links in the
skill detail page install card
- security: update evaluator prompt to recognize envVars alongside
requires.env and primaryEnv
- tests: 7 new test cases covering all declaration formats
* fix(ui): handle unspecified env required state and stable keys
* docs(changelog): credit metadata manifest expansion (#360) (thanks @mahsumaktas)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat(api): expose security evaluation results
- Add security field to skill version API responses
- Map llmAnalysis database field to public API format
- Display security info in CLI inspect command
- Enable security tools like clawsec-clawhub-checker to access internal security checks
Security field includes:
- status: clean|suspicious|malicious|pending|error
- hasWarnings: boolean
- checkedAt: timestamp
- model: evaluation model name
Backward compatible: optional field, no breaking changes.
* fix: ensure hasWarnings is always boolean
- Add ?? false to coerce undefined to false when dimensions is undefined
- Fixes Greptile comment: hasWarnings can be undefined instead of boolean
- Ensures SecurityStatusSchema validation passes on client side
* Update convex/httpApiV1/skillsV1.ts
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
* fix(api-cli): harden security inspect output + tests (#362) (thanks @abutbul)
---------
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): handle missing browser opener gracefully
On headless Linux servers without xdg-open, 'clawhub login' crashes with
ENOENT error. This change catches the error and prints the URL for manual
copy-paste instead of crashing.
Fixes crash on:
- VPS/cloud servers
- Docker containers
- CI environments
- WSL without browser integration
* fix(cli): test browser-opener fallback messaging (#163) (thanks @aronchick)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: surface platform/architecture labels on skill cards and API
Expose existing `os` and `nix.systems` metadata from skill frontmatter
through the HTTP API and render as compact tags on browse/search views.
- Widen `PublicSkillListVersion` and `SkillListEntry` types to include
`os` and `nix.systems` fields (data already flows through, types were
artificially narrow)
- Add `metadata: { os, systems }` to `/api/v1/skills/{slug}` and
`/api/v1/skills` list responses
- Add `formatSystemsList` and `getPlatformLabels` helpers to map nix
system strings to human-readable labels (e.g. aarch64-darwin → macOS ARM64)
- Add `platformLabels` prop to `SkillCard`, render as `.tag .tag-compact`
- Show platform labels in both card grid and list views
- Update HTTP API docs with new `metadata` field
Coded by Claude Opus 4.6 (Claude Code)
Reviewed and tested by Jason (@asyncjason)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: remove redundant optional chaining on clawdis
Address greptile-apps review comment — clawdis is already confirmed
truthy by the ternary condition, so `?.` is unnecessary.
Coded by Claude Opus 4.6 (Claude Code)
Reviewed and tested by Jason (@asyncjason)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: include version data in listPublicPageV2 for platform labels
The browse listing passed includeVersion: false, causing latestVersion
to always be null and platform/arch labels to never render.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Jason Separovic <jason@wilma.dog>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* docs: add CONTRIBUTING.md and refresh README header
Add a comprehensive CONTRIBUTING.md covering local Convex setup,
env var configuration, GitHub OAuth, JWT keys, database seeding,
CLI development, PR guidelines, and AI-generated code policy.
Refresh the README with a centered logo, quick links row, and
clickable doc references. Condense the Local dev section to link
to CONTRIBUTING.md for full setup details.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: add #clawhub discord channel
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: prevent filtered skills pagination flicker
Skip fully filtered-out pages in public skills pagination so highlighted/non-suspicious filtering doesn't return empty pages with more cursor state, which caused repeated loading-more flicker.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix: rely on inferred Convex paginate result type
Remove the custom runPaginate annotation so TypeScript infers the exact Convex paginate result shape and preserves stronger type-safety.
Co-authored-by: Cursor <cursoragent@cursor.com>
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Retry-After was set to an absolute Unix epoch timestamp (e.g. 1771404540),
which violates RFC 9110 §10.2.3. Clients treating it as delay-seconds
would wait ~56 years. Now emits the actual seconds until reset.
Closes#407
Address review feedback:
- Use undici's EnvHttpProxyAgent instead of ProxyAgent. This properly
handles HTTPS_PROXY vs HTTP_PROXY per-scheme, respects NO_PROXY,
and uses connect.timeout instead of requestTls.
- Update docs to mention NO_PROXY support.
The CLI creates a custom undici Agent via setGlobalDispatcher() which
overrides any proxy configuration. Since Node.js native fetch (backed
by undici) does not automatically respect HTTP_PROXY/HTTPS_PROXY env
vars, the CLI fails with 'fetch failed' on systems that require a
proxy for outbound connections.
Import ProxyAgent from undici and use it when any of the standard proxy
environment variables (HTTPS_PROXY, HTTP_PROXY, https_proxy, http_proxy)
is set. When no proxy variable is present, behavior is unchanged.
Also adds proxy documentation to cli.md and a troubleshooting entry.
Address review feedback:
- Guard rescan de-escalation with `status === 'clean'` so pending/unknown
verdicts don't accidentally clear the suspicious flag
- Fix approveSkillByHashInternal where `alreadyFlagged` in the condition
`(isSuspicious || alreadyFlagged) && !bypassSuspicious` prevented clean
verdicts from reaching the isClean branch that properly checks whether
a different scanner set the flag
The daily VT rescan updated vtAnalysis on the version but only called
escalateByVtInternal for suspicious/malicious verdicts. When a verdict
improved from suspicious to clean, the version's vtAnalysis was updated
(website shows "Benign") but the skill's moderationFlags kept the stale
"flagged.suspicious" entry (CLI warns "suspicious"). Now the rescan
calls approveSkillByHashInternal to clear the flag on de-escalation.
Avoids leaving an explicit undefined key in the badges object which
could fail Convex validation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add backfillDenormalizedBadgesInternal: syncs skillBadges table →
skill.badges field so listing/search reads are correct
- Simplify hydrateResults fallback
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove badge table queries from listing and search paths (~200 queries
per page load eliminated). Use denormalized skill.badges field instead.
- Sync skill.badges when badges are mutated (upsertSkillBadge/removeSkillBadge).
- Add embeddingSkillMap lookup table (~100 bytes/doc) so search hydration
can skip reading full skillEmbeddings docs (~12KB each with vector).
- Remove dead badge query exports from search module.
- Reduce lexical fallback scan limit from 1200 to 500.
- Add backfill mutation for embeddingSkillMap with graceful fallback.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Skills should never have more than a handful of badge records.
Using .take(10) instead of .collect() avoids unbounded reads.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The 5-minute stat event processor was patching skill documents on every run,
which invalidated listPublicPageV2 reactive queries for ALL subscribers —
causing a thundering herd responsible for ~17 TB (59%) of the 28.65 TB
monthly db bandwidth.
Split into two paths:
- Daily stats (15-min cron): writes to skillDailyStats only, no skill doc patches
- Skill doc sync (6-hour cron): patches skill documents with accumulated deltas
Also skip reading version docs in listPublicPageV2 and search hydration
(version data is only needed on detail pages, not listings).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Prevent activating skills with quality.low moderation reason
- Add skill lookup and moderationReason check in 3 locations where skills are activated
- This ensures quality gate quarantine is not bypassed when VT scan is unavailable or stale
Resolves review comments on #300
Published skills stay permanently hidden in search when VirusTotal
cannot produce a verdict. Three code paths leave moderationStatus as
'hidden' with no recovery:
1. VT_API_KEY not configured — scan skipped, skill stays hidden
2. VT hash not found after 10 poll attempts — marked stale, stays hidden
3. VT hash found but no Code Insight after 10 attempts — same
Fix: call setSkillModerationStatusActiveInternal in all three paths so
the skill becomes searchable. If VT later returns a malicious verdict,
approveSkillByHashInternal will correctly re-hide and flag it.
Closes#139
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Show 'Loading skills…' instead of 'No skills match' when pagination is not exhausted
- Hide 'Scroll to load more' when results are empty
- Add tests for both cases
* fix: return proper HTTP status codes for delete/undelete errors
The delete and undelete handlers for skills and souls were catching all
errors and returning 401 Unauthorized, even for errors like:
- 'Skill not found' (should be 404)
- 'Forbidden' (should be 403)
- Other validation errors (should be 400)
This change updates the error handling to return appropriate status codes:
- 401 Unauthorized: authentication failures
- 403 Forbidden: authorization failures (not owner/admin/moderator)
- 404 Not Found: skill/soul/user not found
- 400 Bad Request: other errors with descriptive message
Fixes#34
* fix(cli): use proper Error objects in abort timeouts
When AbortController.abort() receives a string instead of an Error,
the string itself is thrown. pRetry then wraps it in a confusing
message: 'Non-error was thrown: Timeout'
Changed all 3 occurrences in http.ts:
- apiRequest (line 57)
- apiRequestForm (line 106)
- downloadZip (line 141)
Now timeouts will surface as proper Error objects with clear messages.
* test: add e2e test for delete error handling
Verifies that deleting a non-existent skill returns a proper 'not found'
error instead of a generic 'Unauthorized' message.
* fix: use Error for timeout abort in e2e helper
* feat: add skill file viewer
* fix: prevent file viewer state updates after unmount
* feat: add ban reasons to moderation
* chore: release 0.6.0
* docs: reset changelog for next release
* feat: add LLM security evaluation at publish time
Add OpenClaw LLM-based security evaluator that runs alongside VirusTotal
when skills are published. Reads SKILL.md prose, metadata, install specs,
and file manifest, then assesses coherence across 5 dimensions to catch
social engineering vectors that VT/regex miss (e.g. instruction-only skills
with no code files).
- convex/lib/securityPrompt.ts: system prompt, message assembly, response
parsing, injection pattern detection
- convex/llmEval.ts: evaluateWithLlm action, evaluateBySlug convenience
action, backfillLlmEval for existing skills
- convex/schema.ts: llmAnalysis field on skillVersions
- convex/skills.ts: updateVersionLlmAnalysisInternal mutation,
getActiveSkillBatchForLlmBackfillInternal query, defense-in-depth
multi-scanner flag merging in approveSkillByHashInternal
- convex/lib/skillPublish.ts: schedule LLM eval alongside VT scan
- SkillDetailPage.tsx: OpenClaw row, LlmAnalysisDetail expandable
component with 5 dimension rows, guidance panel, findings section
- styles.css: analysis detail styles from mockup
* fix: collapse OpenClaw analysis by default, fix row spacing, switch to gpt-5-mini
* fix: add retry with backoff for OpenAI rate limits, fix JSON mode requirement
* fix: increase max_output_tokens for reasoning model, fix backfill error retry
* feat: recognize metadata.openclaw as valid frontmatter namespace
* fix: eval assembler falls back to metadata.openclaw for requirements
* feat: evaluator reads all file contents, not just SKILL.md
Reads all files from storage and includes their full source in the eval
prompt so the LLM can detect malicious code hidden behind clean READMEs.
Injection detection now scans all content. Per-file cap 10K chars, total
cap 50K chars.
* feat: add skill metadata docs, suspicious appeal banner for owners
- Document full frontmatter metadata reference in docs/skill-format.md
- Add metadata section + quick example to README
- Show appeal message on suspicious skills (owner-only) linking to GitHub issues
- Accept metadata.openclaw alias in README docs
- Re-evaluate all skills with full file content reading (backfill in progress)
* fix: trailing comma tolerance in JSON metadata, tone down persistence flags
- Strip trailing commas in frontmatter JSON before parsing (silent failure fix)
- Stop flagging disable-model-invocation default as a concern (it's the normal default)
- Stop flagging skills configuring themselves as privilege escalation
- Add MITRE ATLAS AML.T0051 context for when autonomous invocation actually matters
- Show actual defaults in assembled eval message instead of "not set"
* chore: fix lint issues (#213)
* perf: lazy-load diff viewer (Monaco) (#212)
* chore: fix review comments
* fix: VT scan sync race condition + LLM-first moderation model
VT no longer overwrites LLM moderation verdicts. LLM is the primary
moderation authority; VT only escalates (hides + flags) for malicious/
suspicious content via new escalateByVtInternal mutation. Stale VT polls
write vtAnalysis marker instead of overwriting moderationReason. Query
pools expanded to include LLM-evaluated skills awaiting VT results.
Ban message now references malicious skills and security@openclaw.ai.
* fix: handle GitHub API rate limits in account age check (#246)
* fix: handle GitHub API rate limits in account age check
The GitHub account lookup uses unauthenticated requests (60 req/hr
per IP). Since this runs server-side in Convex, all users share the
same IP and quickly exhaust the rate limit, causing "GitHub account
lookup failed" errors during skill publish.
- Detect 403/429 responses and surface a clear rate-limit message
- Support optional GITHUB_TOKEN env var for authenticated requests
(5,000 req/hr)
Fixes#155
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: stabilize GitHub account gate tests and docs
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* docs: thank @superlowburn for PR #246
* fix: prioritize relevant skills in search
* fix: add lexical fallback for skill search recall
* test: add search fallback coverage
* test: fix search test handler typing
* fix(http): remove allowH2 from undici Agent — causes fetch failed on Node.js 22+ (#245)
* Remove allowH2 option from global dispatcher
fix/remove-allowH2-undici-node22-compat
* fix(http): remove allowH2 from e2e dispatcher
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* docs: add 0.6.1 unreleased changelog from post-0.6.0 commits
* fix: allow soft-deleted users to re-authenticate
Fixes Issue #32 where users who soft-deleted their accounts were unable to sign back in because the re-auth logic was only triggering when an existingUserId was passed by the auth provider, which doesn't happen during a standard fresh login flow.
* test: update auth tests for direct deletedAt check
* fix: restore existingUserId check for type safety
* fix: update tests to include required existingUserId parameter
* fix: resolve final lint error in auth tests
* fix: ensure reactivation only matches soft-deleted user (prevents bypass)
* fix: allow re-auth when existingUserId is null
* fix: use valid crons.interval and set to 1 minute
* test: add missing coverage for fresh-login reactivation and identity mismatch guard
* fix: scope reauth fix; keep banned users blocked (#177) (thanks @tanujbhaud)
* fix: include comment deltas in action-based stat processing & add stats reconciliation (#194)
Bug 1: applyAggregatedStatsAndUpdateCursor was missing 'comments' in both
the guard condition and the applySkillStatDeltas call. This caused comment
count deltas to be silently dropped during cron-based event processing,
while stars/downloads/installs were processed correctly.
Bug 2: No reconciliation mechanism existed. If events were missed due to
cursor issues or processing errors, skill stats (stars, comments) would
remain stale with no way to recover. Added reconcileSkillStarCounts
maintenance mutation that counts actual records in the stars and comments
tables and patches any out-of-sync skill stats.
Fixes#193
Co-authored-by: Limitless2023 <limitless@users.noreply.github.com>
* fix: prevent horizontal overflow from long code blocks in skill pages (#183)
* Fix: Prevent horizontal overflow from long code blocks in skill pages
- Add max-width: 100% to .file-list-body and .file-row
- Prevents page-wide overflow when skills contain long code examples
- Markdown pre blocks already have overflow-x: auto, but parent containers were expanding infinitely
- Fixes issue where skills with 400+ char lines (e.g. browser automation commands) cause horizontal scrolling
Affected: Skills with long inline code in markdown (browser act commands, etc.)
* fix: add max-width to .file-list container to prevent overflow
- Also ensures .file-list-body constraint is inherited properly
- Prevents long code blocks from expanding file list container
* fix: add max-width to all markdown containers and pre tags
- Add max-width: 100% to .markdown, .tab-body, .markdown pre
- Ensures code blocks are constrained and show horizontal scrollbar
- Prevents content from expanding parent containers beyond viewport
* fix: add overflow-x to parent containers for horizontal scroll
Adds overflow-x: auto to .skill-detail-stack, .tab-card, and .tab-body
to ensure long code blocks are scrollable within the content area
instead of causing page-wide horizontal overflow.
Fixes horizontal overflow issue on skill pages with long code examples
(e.g., browser automation commands with 400+ character lines).
Tested on zepto skill page - page now stays within viewport (1200px)
and code blocks are accessible via horizontal scrollbar in tab area.
* docs: note code-block overflow fix in changelog (#183) (thanks @bewithgaurav)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* chore(release): 0.6.1
* fix: prevent infinite loading loop on skills page (#90)
* fix: prevent infinite loading loop on skills pageAdd isLoadingMore guard to IntersectionObserver useEffect to preventcontinuous WebSocket queries when user is idle at bottom of page.The observer now won't set up while a request is in progress, breakingthe infinite loop cycle.Fixes: Related to #89
* fix: prevent repeated skills auto-load requests (#90) (thanks @xcqtnr)
* fix: resolve PR merge conflicts and keep observer regression test (#90) (thanks @xcqtnr)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): secure config file permissions (#164)
* fix(cli): secure config file permissions and reduce duplication
Security:
- Config files now created with 0600 permissions (owner read/write only)
- Config directories created with 0700 permissions
- Protects API tokens from other users on shared systems
Maintainability:
- Extract resolveConfigPath() helper to reduce code duplication
- Same legacy fallback logic (clawhub -> clawdhub) now in one place
* fix(cli): tolerate unsupported chmod errors for config
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: make /search host-aware in SSR (#257)
* fix: make /search mode-aware
Notes:\n- Medium: /search now depends on getSiteMode() during beforeLoad. On server-side routing, if VITE_SITE_MODE isn’t set and VITE_SOULHUB_SITE_URL is set (as in .env.local), getSiteMode() will resolve to souls and redirect /search to / even on the ClawdHub deployment. This is a regression risk vs the old always-/skills redirect. Confirm deployment envs guarantee correct mode. src/routes/search.tsx:9-31
* fix: make /search host-aware in SSR
* chore: fix lint and route tree for /search route
---------
Co-authored-by: Sash Zats <sash@zats.io>
* fix(vt): explicit return types and missing undici dependency (#255)
* fix(vt): explicit return types and missing undici dependency
Refactor action handlers in convex/vt.ts to use explicit return types, resolving circular type inference (TS7022). Also add undici to devDependencies for E2E tests.
* fix: add root undici devDependency for e2e (#255) (thanks @tanujbhaud)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* Fix initial skill sorting (#92)
* fix: initial skill sorting
* chore: update unit test
* fix: use correct indexes for skill sorting
* chore: cleanup
* fix: land skill sorting update (#92) (thanks @bpk9)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: harden download rate limiting and dedupe (#43) (thanks @regenrek)
- add download-specific rate limit tier\n- add per-IP/day dedupe + daily pruning\n- keep moderation gating + deterministic zips\n- add optional forwarded-IP trust via TRUST_FORWARDED_IPS
* fix: harden skill listing and rate limiting under load
* fix: replace skill report prompt with modal
* fix: add skill publish anti-spam caps and quarantine
* docs: add git local-branch cleanup fallback
* fix: enforce quality gate and trust-tier spam checks
* fix: prevent autobanned users from self-reactivating
* test: expand reauth ban regression coverage
* feat: add empty-skill cleanup backfill with ban nominations
* fix: make empty-skill cleanup resumable
* feat: add non-suspicious skills filter toggle
* style: polish selected states in skills toolbar
* feat: default skills sort to downloads
* fix: enforce downloads as canonical default skills sort
* fix: force canonical downloads sort in skills browse mode
* fix: bypass suspicious flags for privileged owners and polish comment delete UI
* fix: add privileged-owner suspicious flag reconciler
* fix: force auth redirects and registry to canonical clawhub host
* feat: auto-generate missing skill summaries
* fix: make skill summary backfill resumable
* feat: add self-scheduling skill summary backfill job
* perf: short-circuit empty skill summary generation
* style: polish upload page layout and actions
* feat: show popular non-suspicious skills on homepage
* fix: normalize legacy skill stats to prevent homepage crash
* fix: render homepage popular cards from nested skill entries
* style: refine global UI theme, borders, and spacing
* fix: resolve search timeout and improve skills page UI alignment (#53)
* fix: resolve search timeout and improve skills page UI alignment
- Added a 10s timeout to OpenAI embedding requests to prevent hanging searches.
- Fixed a TypeScript error in search.ts regarding entry hydration.
- Restructured skills page layout and CSS to ensure consistent alignment between the search toolbar and skill cards.
* fix: resolve search timeout and improve skills page UI alignment
- Added a 10s timeout to OpenAI embedding requests to prevent hanging searches.
- Fixed a TypeScript error in search.ts regarding entry hydration.
- Restructured skills page layout and CSS to ensure consistent alignment between the search toolbar and skill cards.
* style: format skills index layout block
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* docs: thank @GhadiSaab for #53
* style: shift UI palette to cool blue tones
* style: remove remaining warm accent literals
* style: darken hero primary CTA in dark mode
* fix: show stars in popular skill cards
* fix: simplify skills CTA label
* fix: dedupe download metrics hourly by user-or-ip identity (#278)
* style: restore brown palette and dark-mode CTA tone
* fix(comments): stop updating skills.updatedAt on comment add/remove (#55)
* fix(comments): stop updating skills.updatedAt on comment add/remove
Comments are not content changes, so they shouldn't invalidate skill
list queries that depend on updatedAt. This reduces query invalidation
when users add or remove comments.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* test(comments): add updatedAt invalidation regression coverage
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* refactor(comments): extract handlers and harden mutation tests
* feat: make account deletion irreversible and migrate lint to oxlint
* chore: add oxfmt config
* fix(cli): throw Error for all timeout aborts (#283)
* fix(cli): throw Error on timeout aborts
Users have seen an elevated number of:\n clawdhub search image\n ✖ Non-error was thrown: "Timeout". You should only throw errors.\n\nInvestigation shows we were aborting with a string instead of an Error. Switching to controller.abort(new Error('Timeout')) makes retries/formatting treat it as a real error and clears the message.\n\nExample after change:\n clawdhub search image\n table-image v1.0.0 Table Image (0.332)\n nano-banana-pro v1.0.1 Nano Banana Pro (0.319)\n vap-media v1.0.1 AI media generation API - Flux2pro, Veo3.1, Suno Ai (0.281)\n clawdbot-meshyai-skill v0.1.0 Meshy AI (0.276)\n venice-ai-media v1.0.0 Venice AI Media (0.274)\n daily-recap v1.0.2 Daily Recap (0.260)\n openai-image-gen v1.0.1 Openai Image Gen (0.260)\n bible-votd v1.0.1 Bible Verse of the Day (0.248)\n orf v1.0.1 ORF (0.224)\n smalltalk v1.0.1 Smalltalk (0.161)
* fix(http): wrap fetch calls in try-finally to prevent timer leaks
Addresses Vercel review comment: clearTimeout was not called on error paths when fetch throws an exception.
* fix(cli): unify timeout abort handling
---------
Co-authored-by: Sash Zats <sash@zats.io>
* refactor(cli): centralize HTTP status errors and timeout tests (#286)
* fix: keep new skill versions pending until VT verdict
* style: remove residual blue accents and warm base palette
* fix: add retry logic for OpenAI embedding API failures (#272)
* fix: add retry logic for OpenAI embedding API failures
Fixes#149
When importing or uploading skills, the OpenAI embedding API call could
fail with transient errors (rate limits, timeouts, network issues),
causing the entire import to fail with a generic "Server Error".
This adds retry logic with exponential backoff (1s, 2s, 4s delays):
- Retries on 429 (rate limit) and 5xx server errors
- Retries on network/fetch errors
- Logs warnings for debugging
- Max 3 retries before failing with clear error message
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: correct retry count and broaden network error catch
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: address retry loop off-by-one, broaden error catch, preserve original error
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden embeddings retry semantics
* style: format embeddings retry changes
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: sync handle on user ensure
* fix: sync handle on user ensure (#293) (thanks @christianhpoe)
* feat: improve moderation/admin UX + language-aware quality gate
- API: owner-visible responses for hidden/soft-deleted skills\n- Admin: add unban user mutations + docs\n- Quality: Intl.Segmenter tokenization + CJK signal to reduce false rejects\n- Jobs: skill-stat-events interval 15m -> 5m\n- Tests: add coverage for owner-visible states + non-Latin docs\n- Changelog: add Unreleased entry
* refactor: simplify user ensure updates
* fix(cors): complete CORS + tokenized CLI reads (#296)
* fix(cors): add Access-Control-Allow-Origin headers to API and downloads
* fix: add CORS to error/raw paths & add CLI install auth
* fix: add OPTIONS handler for CORS preflight
* fix(cors): complete CORS + tokenized CLI reads
* test(cli): fix config mock typing
---------
Co-authored-by: Grenghis-Khan <63885013+Grenghis-Khan@users.noreply.github.com>
* refactor: centralize CORS + CLI auth token (#297)
* refactor(convex): centralize CORS headers
* refactor(cli): centralize auth token lookup
* fix(skills): keep global sorting across pagination (#98)
* fix: initial skill sorting
* chore: update unit test
* fix: use correct indexes for skill sorting
* chore: cleanup
* fix(skills): preserve server order for paginated sorting
* chore(lint): apply biome formatting fixes
* chore(convex): bump tsconfig lib to ES2022
* fix(skills): add deterministic tie-breaker for search sorting
* fix(skills): stable sorting across pagination (#98) (thanks @CodeBBakGoSu)
---------
Co-authored-by: Brian Kasper <bkasperr@gmail.com>
Co-authored-by: knox-glorang <knox@glorang.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* chore: drop convex-helpers (#302)
* perf: batch tag resolution to reduce action→query round-trips
- Add getVersionsByIds batch query to skills.ts and souls.ts
- Replace per-item tag resolution with batch resolution in httpApiV1.ts
- Reduces N action→query round-trips to 1 for list endpoints
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: add null guard and short-circuit for empty tags
- Short-circuit when no version IDs to resolve
- Add null coalescing for runQuery response
- Fixes potential crash when tags are empty or query returns null
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* refactor: batch resolve tags in v1 API (#112) (thanks @mkrokosz)
* fix: handle duplicate Convex Auth user records in publish ownership check (#180)
* fix: handle duplicate user records in publish ownership check
* fix: heal publish ownership via GitHub auth identity
---------
Co-authored-by: Emmet Brown <emmet@Emmets-Mac-mini.local>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: gate publish by immutable GitHub account ID
* refactor: simplify GitHub age gate cache
* fix(api): centralize v1 soft-delete error mapping
* chore(cli): align http client with main
* test(api): cover v1 soft-delete error mapping
* test(api): reposition soft-delete mapping test
* fix: default to CF-only client IP parsing
* docs: changelog credit + v1 delete status codes
* fix(cli): clarify logout only affects local config (#166)
* fix(cli): clarify logout only affects local config
Users may assume 'clawhub logout' revokes their token everywhere.
In reality, the token remains valid on the server until explicitly
revoked in the web UI. This could be a security concern on shared
machines.
Update the message to set correct expectations.
* fix(cli): clarify logout revocation scope (#166) (thanks @aronchick)
* chore: sync changelog for merge (#166) (thanks @aronchick)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: anti-squatting protection, backup restore, and ban flow improvements (#298)
* feat: anti-squatting protection, backup restore, and ban flow improvements
- Add `reservedSlugs` table with 90-day cooldown to prevent slug squatting
after skill deletion. Hard-delete finalize phase reserves slugs for the
original owner; `insertVersion` blocks non-owners during cooldown.
- Change ban flow from hard-delete to soft-delete: `banUserWithActor` now
sets `moderationReason: 'user.banned'` and syncs embedding visibility.
`unbanUserWithActor` restores all ban-hidden skills and releases slug
reservations automatically.
- Align `autobanMalwareAuthorInternal` with the same soft-delete + embedding
visibility pattern so unban recovery works uniformly.
- Add admin `reclaimSlug` / `reclaimSlugInternal` mutations for reclaiming
squatted slugs, with audit logging.
- Add GitHub backup restore system (`githubRestore.ts`,
`githubRestoreMutations.ts`, `githubRestoreHelpers.ts`) that reads from
the `clawdbot/skills` backup repo and re-creates skill records. Squatter
eviction runs synchronously in the same transaction as restore to avoid
async race conditions.
- Add `POST /api/v1/users/restore` and `POST /api/v1/users/reclaim` admin
HTTP endpoints for bulk operations.
- Add `trustedPublisher` flag on users; trusted publishers bypass the
`pending.scan` auto-hide for new skill publishes.
- Add `setTrustedPublisher` / `setTrustedPublisherInternal` admin mutations.
Addresses: slug squatting prevention, skill backup/restore, ban recovery,
and trusted publisher workflow improvements.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix: harden restore/reclaim + ban flow (#298) (thanks @autogame-17)
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* refactor: post-#298 cleanup (#313)
* refactor: consolidate slug + embedding helpers
* refactor: batch ban/unban skill updates
* refactor: report batched ban/unban scheduling
* fix: unblock package typecheck
* refactor: split httpApiV1 + consolidate moderation batches (#315)
* refactor: dedupe v1 file response + unify embedding patches (#316)
* Devin/1771112524 skill metadata update (#312)
* fix: sync GitHub profile on login to handle username renames (#303)
When a user renames their GitHub account, the stored username becomes stale
and causes 'GitHub account lookup failed' errors during skill publishing.
This fix:
- Adds syncGitHubProfile function that fetches current profile using the
immutable GitHub numeric ID
- Adds syncGitHubProfileInternal mutation to update user's name, handle,
displayName, and image when they change
- Schedules the sync as a background action on every login via
afterUserCreatedOrUpdated callback
The sync is best-effort (silently fails if GitHub API unavailable) since
it's not on the critical path. It only updates fields if the username
has actually changed.
Fixes#303
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: allow updating skill summary/description on subsequent publishes (#301)
Previously, the skill summary was only extracted from metadata.description
in the SKILL.md frontmatter. This change also checks for a direct
'description' field in the frontmatter, ensuring that users can update
their skill description by modifying either location.
The fix prioritizes the new description from the current publish over
the existing skill summary, allowing updates to be reflected correctly.
Fixes#301
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: throttle GitHub profile sync
* feat: show skill owner avatars
* fix: avoid nested owner links
* refactor: centralize profile sync + owner lookup
* docs: changelog for #312 (thanks @ianalloway)
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* style: polish markdown code blocks
* feat: show skill owner avatars on home + lists
* feat: sync GitHub profile name
* feat: improve skill card meta layout
* fix: make ghost buttons look like buttons
* fix: match skill hero cta widths
* fix: prefer $HOME over os.homedir() for path resolution (#299)
* fix: prefer $HOME over os.homedir() for path resolution
os.homedir() reads from /etc/passwd which can return a stale path
after a Linux user rename (usermod -l). Prefer the $HOME environment
variable which reflects the current session.
Closes#82
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: normalize resolveHome output
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* UI: allow copying security scan summary text (#322)
* fix(ui): prevent analysis toggle when selecting summary (#324)
* feat: add uninstall command for skills (#241)
* feat: add uninstall command for skills
Implements `clawhub uninstall <slug>` to properly remove installed skills.
Changes:
- Added cmdUninstall function in skills.ts
- Validates skill is installed before removal
- Removes skill directory and lockfile entry
- Supports --yes flag to skip confirmation prompt
- Added comprehensive test coverage
Closes#221
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: require --yes in non-interactive mode and update lockfile before rm
Address review feedback:
- Fail with "Pass --yes (no input)" when running non-interactively
without --yes flag, matching delete/star/unstar/moderation commands
- Update lockfile before removing directory to avoid inconsistent state
if rm succeeds but writeLockfile fails
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden skill uninstall flow (#241) (thanks @superlowburn)
* docs: document uninstall CLI command (#241) (thanks @superlowburn)
* test: fix cmdUninstall mock typing (#241) (thanks @superlowburn)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: add skill file viewer
* fix: prevent file viewer state updates after unmount
* fix: lazy-load skill file viewer (#44) (thanks @regenrek)
---------
Co-authored-by: Sergiy Dybskiy <s@serg.tech>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
Co-authored-by: theonejvo <theonejvo@users.noreply.github.com>
Co-authored-by: Vignesh <vigneshnatarajan92@gmail.com>
Co-authored-by: Steve <superlowburn@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: DColl <david.coll.78@gmail.com>
Co-authored-by: Tanuj Bhaud <tanujbhaud@gmail.com>
Co-authored-by: Limitless <127183162+Limitless2023@users.noreply.github.com>
Co-authored-by: Limitless2023 <limitless@users.noreply.github.com>
Co-authored-by: Gaurav Sharma <sharmag@microsoft.com>
Co-authored-by: xcqtnr <xcqtnr0.0@gmail.com>
Co-authored-by: David Aronchick <aronchick@gmail.com>
Co-authored-by: Sash Zats <sash@zats.io>
Co-authored-by: Tanuj Bhaud <128238320+tanujbhaud@users.noreply.github.com>
Co-authored-by: Brian Kasper <brian@bkasper.com>
Co-authored-by: ghadi saab <ghadisaab21@gmail.com>
Co-authored-by: sethconvex <seth@convex.dev>
Co-authored-by: ChristianHPoe <chpoensgen@me.com>
Co-authored-by: Grenghis-Khan <63885013+Grenghis-Khan@users.noreply.github.com>
Co-authored-by: CodeBBakGoSu <127713112+CodeBBakGoSu@users.noreply.github.com>
Co-authored-by: Brian Kasper <bkasperr@gmail.com>
Co-authored-by: knox-glorang <knox@glorang.com>
Co-authored-by: Matthew Krokosz <mattkrokosz@gmail.com>
Co-authored-by: emmet-bot <emmet@universaleverything.io>
Co-authored-by: Emmet Brown <emmet@Emmets-Mac-mini.local>
Co-authored-by: autogame-17 <166480271+autogame-17@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Ian Alloway <adapter_burners.1y@icloud.com>
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: CleanApp <165804662+borisolver@users.noreply.github.com>
* feat: add uninstall command for skills
Implements `clawhub uninstall <slug>` to properly remove installed skills.
Changes:
- Added cmdUninstall function in skills.ts
- Validates skill is installed before removal
- Removes skill directory and lockfile entry
- Supports --yes flag to skip confirmation prompt
- Added comprehensive test coverage
Closes#221
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: require --yes in non-interactive mode and update lockfile before rm
Address review feedback:
- Fail with "Pass --yes (no input)" when running non-interactively
without --yes flag, matching delete/star/unstar/moderation commands
- Update lockfile before removing directory to avoid inconsistent state
if rm succeeds but writeLockfile fails
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden skill uninstall flow (#241) (thanks @superlowburn)
* docs: document uninstall CLI command (#241) (thanks @superlowburn)
* test: fix cmdUninstall mock typing (#241) (thanks @superlowburn)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: prefer $HOME over os.homedir() for path resolution
os.homedir() reads from /etc/passwd which can return a stale path
after a Linux user rename (usermod -l). Prefer the $HOME environment
variable which reflects the current session.
Closes#82
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: normalize resolveHome output
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: sync GitHub profile on login to handle username renames (#303)
When a user renames their GitHub account, the stored username becomes stale
and causes 'GitHub account lookup failed' errors during skill publishing.
This fix:
- Adds syncGitHubProfile function that fetches current profile using the
immutable GitHub numeric ID
- Adds syncGitHubProfileInternal mutation to update user's name, handle,
displayName, and image when they change
- Schedules the sync as a background action on every login via
afterUserCreatedOrUpdated callback
The sync is best-effort (silently fails if GitHub API unavailable) since
it's not on the critical path. It only updates fields if the username
has actually changed.
Fixes#303
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: allow updating skill summary/description on subsequent publishes (#301)
Previously, the skill summary was only extracted from metadata.description
in the SKILL.md frontmatter. This change also checks for a direct
'description' field in the frontmatter, ensuring that users can update
their skill description by modifying either location.
The fix prioritizes the new description from the current publish over
the existing skill summary, allowing updates to be reflected correctly.
Fixes#301
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: throttle GitHub profile sync
* feat: show skill owner avatars
* fix: avoid nested owner links
* refactor: centralize profile sync + owner lookup
* docs: changelog for #312 (thanks @ianalloway)
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: anti-squatting protection, backup restore, and ban flow improvements
- Add `reservedSlugs` table with 90-day cooldown to prevent slug squatting
after skill deletion. Hard-delete finalize phase reserves slugs for the
original owner; `insertVersion` blocks non-owners during cooldown.
- Change ban flow from hard-delete to soft-delete: `banUserWithActor` now
sets `moderationReason: 'user.banned'` and syncs embedding visibility.
`unbanUserWithActor` restores all ban-hidden skills and releases slug
reservations automatically.
- Align `autobanMalwareAuthorInternal` with the same soft-delete + embedding
visibility pattern so unban recovery works uniformly.
- Add admin `reclaimSlug` / `reclaimSlugInternal` mutations for reclaiming
squatted slugs, with audit logging.
- Add GitHub backup restore system (`githubRestore.ts`,
`githubRestoreMutations.ts`, `githubRestoreHelpers.ts`) that reads from
the `clawdbot/skills` backup repo and re-creates skill records. Squatter
eviction runs synchronously in the same transaction as restore to avoid
async race conditions.
- Add `POST /api/v1/users/restore` and `POST /api/v1/users/reclaim` admin
HTTP endpoints for bulk operations.
- Add `trustedPublisher` flag on users; trusted publishers bypass the
`pending.scan` auto-hide for new skill publishes.
- Add `setTrustedPublisher` / `setTrustedPublisherInternal` admin mutations.
Addresses: slug squatting prevention, skill backup/restore, ban recovery,
and trusted publisher workflow improvements.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix: harden restore/reclaim + ban flow (#298) (thanks @autogame-17)
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): clarify logout only affects local config
Users may assume 'clawhub logout' revokes their token everywhere.
In reality, the token remains valid on the server until explicitly
revoked in the web UI. This could be a security concern on shared
machines.
Update the message to set correct expectations.
* fix(cli): clarify logout revocation scope (#166) (thanks @aronchick)
* chore: sync changelog for merge (#166) (thanks @aronchick)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: handle duplicate user records in publish ownership check
* fix: heal publish ownership via GitHub auth identity
---------
Co-authored-by: Emmet Brown <emmet@Emmets-Mac-mini.local>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
- Short-circuit when no version IDs to resolve
- Add null coalescing for runQuery response
- Fixes potential crash when tags are empty or query returns null
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add getVersionsByIds batch query to skills.ts and souls.ts
- Replace per-item tag resolution with batch resolution in httpApiV1.ts
- Reduces N action→query round-trips to 1 for list endpoints
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: add retry logic for OpenAI embedding API failures
Fixes#149
When importing or uploading skills, the OpenAI embedding API call could
fail with transient errors (rate limits, timeouts, network issues),
causing the entire import to fail with a generic "Server Error".
This adds retry logic with exponential backoff (1s, 2s, 4s delays):
- Retries on 429 (rate limit) and 5xx server errors
- Retries on network/fetch errors
- Logs warnings for debugging
- Max 3 retries before failing with clear error message
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: correct retry count and broaden network error catch
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: address retry loop off-by-one, broaden error catch, preserve original error
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden embeddings retry semantics
* style: format embeddings retry changes
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): throw Error on timeout aborts
Users have seen an elevated number of:\n clawdhub search image\n ✖ Non-error was thrown: "Timeout". You should only throw errors.\n\nInvestigation shows we were aborting with a string instead of an Error. Switching to controller.abort(new Error('Timeout')) makes retries/formatting treat it as a real error and clears the message.\n\nExample after change:\n clawdhub search image\n table-image v1.0.0 Table Image (0.332)\n nano-banana-pro v1.0.1 Nano Banana Pro (0.319)\n vap-media v1.0.1 AI media generation API - Flux2pro, Veo3.1, Suno Ai (0.281)\n clawdbot-meshyai-skill v0.1.0 Meshy AI (0.276)\n venice-ai-media v1.0.0 Venice AI Media (0.274)\n daily-recap v1.0.2 Daily Recap (0.260)\n openai-image-gen v1.0.1 Openai Image Gen (0.260)\n bible-votd v1.0.1 Bible Verse of the Day (0.248)\n orf v1.0.1 ORF (0.224)\n smalltalk v1.0.1 Smalltalk (0.161)
* fix(http): wrap fetch calls in try-finally to prevent timer leaks
Addresses Vercel review comment: clearTimeout was not called on error paths when fetch throws an exception.
* fix(cli): unify timeout abort handling
---------
Co-authored-by: Sash Zats <sash@zats.io>
* fix(comments): stop updating skills.updatedAt on comment add/remove
Comments are not content changes, so they shouldn't invalidate skill
list queries that depend on updatedAt. This reduces query invalidation
when users add or remove comments.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* test(comments): add updatedAt invalidation regression coverage
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: resolve search timeout and improve skills page UI alignment
- Added a 10s timeout to OpenAI embedding requests to prevent hanging searches.
- Fixed a TypeScript error in search.ts regarding entry hydration.
- Restructured skills page layout and CSS to ensure consistent alignment between the search toolbar and skill cards.
* fix: resolve search timeout and improve skills page UI alignment
- Added a 10s timeout to OpenAI embedding requests to prevent hanging searches.
- Fixed a TypeScript error in search.ts regarding entry hydration.
- Restructured skills page layout and CSS to ensure consistent alignment between the search toolbar and skill cards.
* style: format skills index layout block
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(vt): explicit return types and missing undici dependency
Refactor action handlers in convex/vt.ts to use explicit return types, resolving circular type inference (TS7022). Also add undici to devDependencies for E2E tests.
* fix: add root undici devDependency for e2e (#255) (thanks @tanujbhaud)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: make /search mode-aware
Notes:\n- Medium: /search now depends on getSiteMode() during beforeLoad. On server-side routing, if VITE_SITE_MODE isn’t set and VITE_SOULHUB_SITE_URL is set (as in .env.local), getSiteMode() will resolve to souls and redirect /search to / even on the ClawdHub deployment. This is a regression risk vs the old always-/skills redirect. Confirm deployment envs guarantee correct mode. src/routes/search.tsx:9-31
* fix: make /search host-aware in SSR
* chore: fix lint and route tree for /search route
---------
Co-authored-by: Sash Zats <sash@zats.io>
* fix(cli): secure config file permissions and reduce duplication
Security:
- Config files now created with 0600 permissions (owner read/write only)
- Config directories created with 0700 permissions
- Protects API tokens from other users on shared systems
Maintainability:
- Extract resolveConfigPath() helper to reduce code duplication
- Same legacy fallback logic (clawhub -> clawdhub) now in one place
* fix(cli): tolerate unsupported chmod errors for config
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: prevent infinite loading loop on skills pageAdd isLoadingMore guard to IntersectionObserver useEffect to preventcontinuous WebSocket queries when user is idle at bottom of page.The observer now won't set up while a request is in progress, breakingthe infinite loop cycle.Fixes: Related to #89
* fix: prevent repeated skills auto-load requests (#90) (thanks @xcqtnr)
* fix: resolve PR merge conflicts and keep observer regression test (#90) (thanks @xcqtnr)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* Fix: Prevent horizontal overflow from long code blocks in skill pages
- Add max-width: 100% to .file-list-body and .file-row
- Prevents page-wide overflow when skills contain long code examples
- Markdown pre blocks already have overflow-x: auto, but parent containers were expanding infinitely
- Fixes issue where skills with 400+ char lines (e.g. browser automation commands) cause horizontal scrolling
Affected: Skills with long inline code in markdown (browser act commands, etc.)
* fix: add max-width to .file-list container to prevent overflow
- Also ensures .file-list-body constraint is inherited properly
- Prevents long code blocks from expanding file list container
* fix: add max-width to all markdown containers and pre tags
- Add max-width: 100% to .markdown, .tab-body, .markdown pre
- Ensures code blocks are constrained and show horizontal scrollbar
- Prevents content from expanding parent containers beyond viewport
* fix: add overflow-x to parent containers for horizontal scroll
Adds overflow-x: auto to .skill-detail-stack, .tab-card, and .tab-body
to ensure long code blocks are scrollable within the content area
instead of causing page-wide horizontal overflow.
Fixes horizontal overflow issue on skill pages with long code examples
(e.g., browser automation commands with 400+ character lines).
Tested on zepto skill page - page now stays within viewport (1200px)
and code blocks are accessible via horizontal scrollbar in tab area.
* docs: note code-block overflow fix in changelog (#183) (thanks @bewithgaurav)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
Bug 1: applyAggregatedStatsAndUpdateCursor was missing 'comments' in both
the guard condition and the applySkillStatDeltas call. This caused comment
count deltas to be silently dropped during cron-based event processing,
while stars/downloads/installs were processed correctly.
Bug 2: No reconciliation mechanism existed. If events were missed due to
cursor issues or processing errors, skill stats (stars, comments) would
remain stale with no way to recover. Added reconcileSkillStarCounts
maintenance mutation that counts actual records in the stars and comments
tables and patches any out-of-sync skill stats.
Fixes#193
Co-authored-by: Limitless2023 <limitless@users.noreply.github.com>
Fixes Issue #32 where users who soft-deleted their accounts were unable to sign back in because the re-auth logic was only triggering when an existingUserId was passed by the auth provider, which doesn't happen during a standard fresh login flow.
* Remove allowH2 option from global dispatcher
fix/remove-allowH2-undici-node22-compat
* fix(http): remove allowH2 from e2e dispatcher
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: handle GitHub API rate limits in account age check
The GitHub account lookup uses unauthenticated requests (60 req/hr
per IP). Since this runs server-side in Convex, all users share the
same IP and quickly exhaust the rate limit, causing "GitHub account
lookup failed" errors during skill publish.
- Detect 403/429 responses and surface a clear rate-limit message
- Support optional GITHUB_TOKEN env var for authenticated requests
(5,000 req/hr)
Fixes#155
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: stabilize GitHub account gate tests and docs
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
VT no longer overwrites LLM moderation verdicts. LLM is the primary
moderation authority; VT only escalates (hides + flags) for malicious/
suspicious content via new escalateByVtInternal mutation. Stale VT polls
write vtAnalysis marker instead of overwriting moderationReason. Query
pools expanded to include LLM-evaluated skills awaiting VT results.
Ban message now references malicious skills and security@openclaw.ai.
- Strip trailing commas in frontmatter JSON before parsing (silent failure fix)
- Stop flagging disable-model-invocation default as a concern (it's the normal default)
- Stop flagging skills configuring themselves as privilege escalation
- Add MITRE ATLAS AML.T0051 context for when autonomous invocation actually matters
- Show actual defaults in assembled eval message instead of "not set"
- Document full frontmatter metadata reference in docs/skill-format.md
- Add metadata section + quick example to README
- Show appeal message on suspicious skills (owner-only) linking to GitHub issues
- Accept metadata.openclaw alias in README docs
- Re-evaluate all skills with full file content reading (backfill in progress)
Reads all files from storage and includes their full source in the eval
prompt so the LLM can detect malicious code hidden behind clean READMEs.
Injection detection now scans all content. Per-file cap 10K chars, total
cap 50K chars.
- getStatsInternal: derive VT stats from moderationReason instead of
N+1 version lookups that hit the 16MB byte limit
- UI: read cached vtAnalysis from version docs instead of hitting the
live VT API on every page view
- Backfill: add vt-cache-backfill cron (30min) with self-scheduling to
drain the backlog of skills missing cached vtAnalysis
- Daily rescan: cursor-based batching (100/batch) with self-scheduling
instead of loading all skills in one shot
- downloads:increment: remove unnecessary db.get that added skill doc
to read set, causing conflicts with the stat processing cron
- users:ensure: only patch when there are real field changes, skip
unconditional updatedAt bump that forced a write on every call
- comments: route stats through event sourcing (insertStatEvent) instead
of synchronous read-modify-write on the skill doc
- rateLimits: split into query-first check + conditional mutation so
denied requests are conflict-free reads
- skillStatEvents: reduce MAX_SKILLS_PER_RUN from 500 to 50 to shrink
the write set and lower conflict probability with concurrent mutations
Co-Authored-By: theonejvo <theonejvo@users.noreply.github.com>
The download endpoint now checks moderation status before serving zips:
- Pending scan (423): "This skill is pending a security scan by VirusTotal. Please try again in a few minutes."
- Malicious (403): "Blocked: this skill has been flagged as malicious by VirusTotal and cannot be downloaded."
- Removed (410): "This skill has been removed by a moderator."
- Hidden (403): "This skill is currently unavailable."
Closes the supply chain gap where a newly published version could be
downloaded before VT scanning completed.
CLI now checks moderation status before installing skills:
**Suspicious skills** - Shows warning and requires confirmation:
```
⚠️ Warning: "skill-name" is flagged as suspicious by VirusTotal Code Insight.
This skill may contain risky patterns (crypto keys, external APIs, eval, etc.)
Review the skill code before use.
? Install anyway? (y/N)
```
Non-interactive mode requires --force flag.
**Malicious skills** - Blocked entirely:
```
✖ Blocked: skill-name is flagged as malicious
Error: This skill has been flagged as malware and cannot be installed.
```
Changes:
- API now returns `moderation` field with `isSuspicious` and `isMalwareBlocked`
- CLI schema updated to expect moderation field
- cmdInstall and cmdUpdate enforce moderation checks
Thanks to @zackkorman for raising this issue.
The auditLogs.targetId field is v.string() in the schema, so explicitly
convert the Id<'users'> to string to ensure type-safe comparison.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Users who deleted their account were unable to sign in again with the
same GitHub account. The OAuth flow would complete but the user would
remain logged out due to the `deletedAt` field being set.
This fix adds a `createOrUpdateUser` callback that:
1. Detects soft-deleted users during OAuth
2. Checks audit logs to determine if user was BANNED vs SELF-DELETED
3. If banned → throws error "This account has been suspended"
4. If self-deleted → clears `deletedAt` to restore account
Security: Both `deleteAccount` and `banUser` set the same `deletedAt`
field. This fix ensures banned users cannot restore their accounts.
Performance: The callback runs on every sign-in, but the audit log
query ONLY executes for soft-deleted users (rare edge case). Normal
active users just hit a single `if` check - no extra queries. When
the audit log query does run, it uses the `by_target` index for
efficient lookup.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
`??` (nullish coalescing) treats `""` as a valid value, so users
with `handle=""` never get a fallback derived from name/email.
Change to `||` so empty strings fall through to the next candidate.
This affects any user whose handle field is an empty string rather
than null/undefined — e.g. early accounts or migration artifacts.
- Batch size 100 (was 10) - process more per run
- Skip skills checked in last 60 min - avoid hammering same hashes
- After 10 failed checks, mark as pending.scan.stale - drops from queue
- Track scanLastCheckedAt and scanCheckCount on skills
- Add TODO for webhook/notification setup
- Fetch 5x batch size and shuffle to avoid queue head-blocking
- Add getScanQueueHealthInternal to monitor queue status
- Log warnings when queue is unhealthy (>50 pending or >24h stale)
- Return health stats from pollPendingScans
- Add requestRescan() to trigger Code Insight via /analyse endpoint
- Update pollPendingScans to request rescan when no Code Insight
- Add backfillPendingScans for one-time backlog clearing
- Add pollPendingScans action to vt.ts that checks VT for Code Insight verdicts
- Add getPendingScanSkillsInternal query to get skills awaiting scan
- Add vt-pending-scans cron job running every 5 minutes
- Updates skill moderation status when VT analysis is complete
- Malicious skills: visible for transparency, downloads blocked via moderationFlags
- Suspicious skills: visible with warning banner, downloads allowed
- Neither appears in search/listings (not indexed)
- Add isSuspicious flag to moderation info
- Update approveSkillByHashInternal to set moderationFlags properly
- Add warning banner CSS variant for suspicious skills
- Add `source` field to VT results to indicate code_insight vs engines
- Display Code Insight analysis text when AI detects malicious patterns
- Only show "X/Y engines" when traditional AV detection triggers
- Add styled analysis block with red accent for malicious verdicts
* fix: show pending skill page to owners instead of "Skill not found"
When a skill owner uploads a skill that's pending VirusTotal scan,
they now see their skill page with a pending banner instead of
"Skill not found". The banner explains the scan is in progress.
Changes:
- Modified getBySlug query to return skill data for owners even when
moderationStatus is 'hidden' with reason 'pending.scan'
- Added pendingReview flag to query response
- Added pending banner component to SkillDetailPage
- Added CSS for pending banner using existing ClawHub gold theme
* fix: show pending skills on owner's dashboard
Extended the list query to include pending skills when the requester
is viewing their own dashboard. Added "Scanning" badge with gold theme
to indicate skills pending VirusTotal review.
* fix: show all moderation states to owners with appropriate UI
- Owners see their blocked/removed skills with explanatory banners
- Red banner for malware-blocked and removed skills
- Gold banner for pending scan
- Download button hidden for blocked/removed skills
- Added security disclaimer: "Like a lobster shell, security has layers"
- Fixed badges bug (use computed badges, not stale skill.badges)
* feat: make malware-blocked skills publicly visible
Blocked skills are now visible to everyone via direct URL:
- Shows red banner with "security issue detected"
- Displays VT scan results
- No download button
- Still hidden from listings/search
Sends a strong transparency signal about security enforcement.
* fix: allow owners to view pending scan skills (#136)
* fix: make deterministic zip date timezone-safe
* chore: update convex api types
* fix: update changelog for pending scan visibility (#136) (thanks @orlyjamie)
---------
Co-authored-by: theonejvo <theonejvo@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
Blocked skills are now visible to everyone via direct URL:
- Shows red banner with "security issue detected"
- Displays VT scan results
- No download button
- Still hidden from listings/search
Sends a strong transparency signal about security enforcement.
- Owners see their blocked/removed skills with explanatory banners
- Red banner for malware-blocked and removed skills
- Gold banner for pending scan
- Download button hidden for blocked/removed skills
- Added security disclaimer: "Like a lobster shell, security has layers"
- Fixed badges bug (use computed badges, not stale skill.badges)
Extended the list query to include pending skills when the requester
is viewing their own dashboard. Added "Scanning" badge with gold theme
to indicate skills pending VirusTotal review.
When a skill owner uploads a skill that's pending VirusTotal scan,
they now see their skill page with a pending banner instead of
"Skill not found". The banner explains the scan is in progress.
Changes:
- Modified getBySlug query to return skill data for owners even when
moderationStatus is 'hidden' with reason 'pending.scan'
- Added pendingReview flag to query response
- Added pending banner component to SkillDetailPage
- Added CSS for pending banner using existing ClawHub gold theme
Add tests for the deterministic ZIP building utility from PR #130:
- buildSkillMeta function
- buildDeterministicZip with various scenarios
- Verifies deterministic output and _meta.json inclusion
Achieves 100% coverage for skillZip.ts.
Add comprehensive tests for the badges utility functions:
- isSkillHighlighted, isSkillOfficial, isSkillDeprecated
- getSkillBadges with all badge combinations
Improves branch coverage from 50% to 100% for badges.ts.
* feat: implementation of dynamic VirusTotal integration and deterministic ZIPs
* fix: do not show security scan results if hash is missing
* ui: show 'Loading...' instead of 'Pending' while fetching VT results
* security: restrict auto-approval to explicit benign verdicts only
* fix: prioritize AI verdict in results and refine stats fallback
- apply Biome formatting and import ordering across linted files
- fix management useEffect dependencies flagged by Biome
Tests: bun run lint:biome; bun run lint:oxlint
When AbortController.abort() receives a string instead of an Error,
the string itself is thrown. pRetry then wraps it in a confusing
message: 'Non-error was thrown: Timeout'
Changed all 3 occurrences in http.ts:
- apiRequest (line 57)
- apiRequestForm (line 106)
- downloadZip (line 141)
Now timeouts will surface as proper Error objects with clear messages.
The delete and undelete handlers for skills and souls were catching all
errors and returning 401 Unauthorized, even for errors like:
- 'Skill not found' (should be 404)
- 'Forbidden' (should be 403)
- Other validation errors (should be 400)
This change updates the error handling to return appropriate status codes:
- 401 Unauthorized: authentication failures
- 403 Forbidden: authorization failures (not owner/admin/moderator)
- 404 Not Found: skill/soul/user not found
- 400 Bad Request: other errors with descriptive message
Fixes#34
* fix: resolve typecheck and lint errors
* fix: stabilize publish paths and token types
* feat: show published skills on user profile
* fix: document profile published skills (#20) (thanks @njoylab)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
The `cmdUpdate` function was passing a relative path to `apiRequest`
using the `url` property, but `url` expects a full URL. When `url` is
provided, it's used as-is without combining with the registry base URL.
This caused "Failed to parse URL from /api/v1/skills/<slug>" errors
when updating skills that don't have a local fingerprint match.
Changed to use `path` property which correctly combines with the
registry base URL via `new URL(args.path, registry)`.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* fix: relax search token matching to require at least one match
The search was requiring ALL query tokens to exist in the skill's
displayName, slug, or summary. This was too strict and caused valid
results to be filtered out. For example, searching "HTTP API client"
would fail to match skills about "HTTP API" that didn't mention "client".
Changed from `.every()` to `.some()` so at least one token must match,
allowing the vector similarity to determine relevance for the rest.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: update matchesExactTokens to require prefix matching for query tokens
* more inclusive token check
* Update convex/lib/searchText.ts
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
---------
Co-authored-by: Ahmed <ahmed.mire@kaluza.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
- Fix "Explore search" button causing page refresh by using URL params
- Enable /search URL deep linking via beforeLoad redirect
- Fix logo click not closing search mode by properly syncing state with URL
Adds a new `clawdhub explore` command that fetches the most recently
updated skills from the registry, sorted by updatedAt descending.
Usage:
clawdhub explore # Show latest 25 skills
clawdhub explore --limit 10
Output includes slug, version, relative time since update, and summary.
The API endpoint already exists and returns skills sorted by updatedAt,
this just exposes it via the CLI.
- include nix plugin metadata, config requirements, and CLI help
- add config examples and format bundle code blocks
- refresh bundle UI styling and layout
- add dashboard with skill management and upload prefill
- redesign skill detail layout with full-width panels
- refactor modules and format dashboard/upload routes
- Add /dashboard route showing user's published skills
- Add 'Dashboard' link to user dropdown menu in header
- Skills display name, slug, description, stats (downloads, stars, versions)
- 'New Version' button links to upload with pre-populated slug
- Upload route accepts ?updateSlug param to pre-fill form for updates
- Auto-bumps version number when updating existing skill
- Responsive design for mobile
- Empty state with call-to-action for new users
contents:read# Required to scan the code in the PR
steps:
- name:Checkout code
uses:actions/checkout@v4
with:
fetch-depth:0# necessary to support the scoping requirements below
- name:TruffleHog OSS
id:trufflehog
# Use a concrete released ref that resolves in upstream action registry.
# v3 (major tag) is not published by trufflesecurity/trufflehog.
uses:trufflesecurity/trufflehog@v3.93.6
with:
path:./
base:${{ github.event.pull_request.base.sha }}# scope it to the committed files
head:${{ github.event.pull_request.head.sha }}
extra_args:--only-verified --debug
- name:Notify on Failure
if:steps.trufflehog.outcome == 'failure'
run:|
echo "::error::Verified secrets found! This PR contains live credentials that must be rotated immediately."
echo "::notice::If these secrets are already in the commit history, they cannot be removed via a simple removal commit/push. A repository owner can contact GitHub Support to purge the cached data: https://support.github.com/contact/private-information"
- PRs: include summary + test commands run. Add screenshots for UI changes.
- Reject PRs that add skills into source code/repo content directly (for example under `skills/` or seed-only additions intended as published skills). Skills must be uploaded/published via CLI.
## Git Notes
- If `git branch -d/-D <branch>` is policy-blocked, delete the local ref directly: `git update-ref -d refs/heads/<branch>`.
- Security/moderation: add bounded explainable auto-ban reasons for scam comments and protect moderator/admin accounts from automated bans.
- Moderation: banning users now also soft-deletes their authored comments (skill + soul), including legacy cleanup on re-ban.
- Skill metadata: support env vars, dependency declarations, author, and links in parsed manifest metadata + install UI (#360) (thanks @mahsumaktas).
- Quality gate: language-aware word counting (`Intl.Segmenter`) and new `cjkChars` signal to reduce false rejects for non-Latin docs.
- Jobs: run skill stat event processing every 5 minutes (was 15).
- API performance: batch resolve skill/soul tags in v1 list/get endpoints (fewer action->query round-trips) (#112) (thanks @mkrokosz).
- Skills: reserve deleted slugs for prior owners (90-day cooldown) to prevent squatting; add admin reclaim flow (#298) (thanks @autogame-17).
- Moderation: ban flow soft-deletes owned skills (reversible) and removes them from vector search (#298) (thanks @autogame-17).
- LLM helpers: centralize OpenAI Responses text extraction for changelog/summary/eval flows (#502) (thanks @ianalloway).
- Rate limiting: apply authenticated quotas by user bucket (vs shared IP), emit delay-based reset headers, and improve CLI 429 guidance/retries (#412) (thanks @lc0rp).
- Search/listing performance: cut embedding hydration and badge read bandwidth via `embeddingSkillMap` + denormalized skill badges; shift stat-doc sync to low-frequency cron (#441) (thanks @sethconvex).
### Fixed
- Upload: keep folder-picking enabled after page refresh by reapplying `webkitdirectory`/`directory` on the file input ref (#551) (thanks @MunemHashmi).
- Skills hard-delete: delete `commentReports` rows during moderation cleanup to avoid orphaned report records.
- Comments: hide entries authored by deleted/deactivated users in `comments:listBySkill`.
- Admin API: `POST /api/v1/users/reclaim` now performs non-destructive root-slug owner transfer
(preserves existing skill versions/stats/metadata) and clears active slug reservations.
- VirusTotal: use shared AV-engine fallback verdict mapping for pending/backfill flows and keep undetected-only results pending (#591) (thanks @Shuai-DaiDai).
- CLI publish: use a longer multipart upload timeout and normalize abort rejections into proper Errors (#550) (thanks @MunemHashmi).
- CLI: forward optional auth tokens for `search` and `explore` against authenticated registries (#608) (thanks @artdaal).
- Skill metadata: parse top-level `requires.*`, `primaryEnv`, and homepage fallbacks for security review accuracy (#548) (thanks @MunemHashmi).
- Users: sync handle on ensure when GitHub login changes (#293) (thanks @christianhpoe).
- Users/Auth: throttle GitHub profile sync on login; also sync avatar when it changes (#312) (thanks @ianalloway).
- Upload gate: fetch GitHub account age by immutable account ID (prevents username swaps) (#116) (thanks @mkrokosz).
- VT fallback: activate only VT-pending hidden skills when scans are unavailable/stale; keep quality/scanner-blocked skills hidden (#300) (thanks @superlowburn).
- API: return proper status codes for delete/undelete errors (#35) (thanks @sergical).
- API: for owners, return clearer status/messages for hidden/soft-deleted skills instead of a generic 404.
- HTTP/CORS: add preflight handler + include CORS headers on API/download errors; CLI: include auth token for owner-visible installs/updates (#146) (thanks @Grenghis-Khan).
- CLI: clarify `logout` only removes the local token; token remains valid until revoked in the web UI (#166) (thanks @aronchick).
- CLI: validate skill slugs used for filesystem operations (prevents path traversal) (#241) (thanks @superlowburn).
- Skills: keep global sorting across pagination on `/skills` (thanks @CodeBBakGoSu, #98).
- Skills: allow updating skill description/summary from frontmatter on subsequent publishes (#312) (thanks @ianalloway).
- Skills/Web: prevent filtered pagination dead-ends and loading-state flicker on `/skills`; move highlighted browse filtering into server list query (#339) (thanks @Marvae).
- Web: align `/skills` total count with public visibility and format header count (thanks @rknoche6, #76).
- Skills/Web: centralize public visibility checks and keep `globalStats` skill counts in sync incrementally; remove duplicate `/skills` default-sort fallback and share browse test mocks (thanks @rknoche6, #76).
- Moderation: clear stale `flagged.suspicious` flags when VirusTotal rescans improve to clean verdicts (#418) (thanks @Phineas1500).
- CLI: respect `HTTPS_PROXY`/`HTTP_PROXY`/`NO_PROXY` env vars for outbound registry requests, with troubleshooting docs (#363) (thanks @kerrypotter).
- CLI: preserve registry base paths when composing API URLs for search/inspect/moderation commands (#486) (thanks @Liknox).
- API tests: lock `Retry-After` behavior to relative-delay semantics for v1 search 429s (#421) (thanks @apoorvdarshan).
- CLI tests: assert 5xx HTTP responses still perform retry attempts before surfacing final error (#457) (thanks @YonghaoZhao722).
- GitHub import: improve storage/publish failure errors with actionable context; add regression tests for error formatting (#512) (thanks @vassiliylakhonin).
- CLI: show manual URL guidance when automatic browser opening is unavailable; add regression tests for opener errors (#163) (thanks @aronchick).
- API/CLI: expose skill security status in version inspect output, with schema wiring and CLI regression coverage (#362) (thanks @abutbul).
## 0.6.1 - 2026-02-13
### Added
- Security: add LLM-based security evaluation during skill publish.
- Parsing: recognize `metadata.openclaw` frontmatter and evaluate all skill files for requirements.
Welcome! ClawHub is the public skill registry for [OpenClaw](https://github.com/openclaw/openclaw). We appreciate bug fixes, documentation improvements, and feature contributions.
- **Questions?** Ask in [#clawhub on Discord](https://discord.gg/clawd).
- **Bug fixes** — PRs are welcome.
- **New features or architectural changes** — please start with a Discord conversation in #clawhub first so we can align on scope.
## Local Development Setup
### Prerequisites
- [Bun](https://bun.sh/) (Convex CLI runs via `bunx`, no global install needed)
### Install and configure
```bash
bun install
cp .env.local.example .env.local
```
Edit `.env.local` with the following values for **local Convex**:
```bash
# Frontend
VITE_CONVEX_URL=http://127.0.0.1:3210
VITE_CONVEX_SITE_URL=http://127.0.0.1:3210
SITE_URL=http://localhost:3000
CONVEX_SITE_URL=http://127.0.0.1:3210
# Deployment used by `bunx convex dev`
CONVEX_DEPLOYMENT=anonymous:anonymous-clawhub
```
### GitHub OAuth App (for login)
1. Go to [github.com/settings/developers](https://github.com/settings/developers) and create a new OAuth App.
2. Set **Homepage URL** to `http://localhost:3000`.
3. Set **Authorization callback URL** to `http://127.0.0.1:3210/api/auth/callback/github`.
4. Copy the Client ID and generate a Client Secret, then add them to `.env.local`:
```bash
AUTH_GITHUB_ID=<your-client-id>
AUTH_GITHUB_SECRET=<your-client-secret>
```
### JWT keys (for Convex Auth)
Generate the signing keys:
```bash
bunx @convex-dev/auth
```
This outputs `JWT_PRIVATE_KEY` and `JWKS` values — paste them into `.env.local`.
### Run the app
```bash
# Terminal A: local Convex backend
bunx convex dev
# Terminal B: frontend (port 3000)
bun run dev
```
### Seed the database
Populate sample data so the UI isn't empty:
```bash
# 3 sample skills (padel, gohome, xuezh)
bunx convex run --no-push devSeed:seedNixSkills
# 50 extra skills for pagination testing (optional)
bunx convex run --no-push devSeedExtra:seedExtraSkillsInternal
```
To reset and re-seed:
```bash
bunx convex run --no-push devSeed:seedNixSkills '{"reset": true}'
```
### Optional environment variables
These features degrade gracefully without their keys:
| Variable | Purpose |
|----------|---------|
| `OPENAI_API_KEY` | Embeddings and vector search (falls back to zero vectors) |
To show CLI help (recommended for nix plugins), include the `cli --help` output:
```yaml
---
name:padel
description:Check padel court availability and manage bookings via Playtomic.
metadata:{"clawdbot":{"cliHelp":"padel --help\\nUsage: padel [command]\\n"}}
---
```
`metadata.clawdbot` is preferred, but `metadata.clawdis` and `metadata.openclaw` are accepted as aliases.
## Skill metadata
Skills declare their runtime requirements (env vars, binaries, install specs) in the `SKILL.md` frontmatter. ClawHub's security analysis checks these declarations against actual skill behavior.
Full reference: [`docs/skill-format.md`](docs/skill-format.md#frontmatter-metadata)
- Desktop overview shows ClawScan-first current verdict totals, pipeline status, recent scan window, category rollups, and failed scan samples.
- Desktop drilldown shows a selected artifact with ClawScan verdict/category/summary first, followed by pipeline status and supporting scanner evidence.
- Mobile view keeps the management security overview usable at narrow width without overlapping controls.
"text":"Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when..."
},
{
"className":"skill-card-footer",
"text":"by@ivangdavilaUpdated 3w ago1.2k·195k"
}
],
"tagsBelowSummary":false,
"authorToUpdatedGap":14
},
{
"step":"mobile grid context",
"viewport":"mobile",
"children":[
{
"className":"skill-card-tags",
"text":"LinuxmacOSWindows"
},
{
"className":"skill-card-header",
"text":"Self-Improving + Proactive Agent"
},
{
"className":"skill-card-summary",
"text":"Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when..."
"text":"Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when..."
},
{
"className":"skill-card-tags",
"text":"LinuxmacOSWindows"
},
{
"className":"skill-card-footer",
"text":"by@ivangdavilaUpdated 3w ago1.2k·195k"
}
],
"tagsBelowSummary":true,
"authorToUpdatedGap":8
},
{
"step":"mobile grid context",
"viewport":"mobile",
"children":[
{
"className":"skill-card-header",
"text":"Self-Improving + Proactive Agent"
},
{
"className":"skill-card-summary",
"text":"Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when..."
- Rendered the account-ban and artifact-level scanner rejection emails from the real email builders; the account-ban email no longer includes scan-results appeal guidance, while the artifact-level email still includes local scan guidance.
- Captured the dedicated banned-account appeal page from a running local ClawHub preview after `/dashboard?error_description=Account%20banned` redirected to `/account-banned`.
- Rendered the account-ban and artifact-level scanner rejection emails from the real email builders.
- Captured the banned-account sign-in copy from a full-stack local ClawHub preview with local Convex on `/dashboard?error_description=Account%20banned`.
- Rendered the account-ban and artifact-level scanner rejection emails from the real email builders.
- Captured the banned-account sign-in copy from a full-stack local ClawHub preview with local Convex on `/dashboard?error_description=Account%20banned`.
Backend: production Convex read data (`wry-manatee-359`).
Pages captured:
-`/skills?sort=installs&dir=desc` showing prod skill rows and install sort.
-`/search?q=swarm` showing prod search results.
-`/chair4ce/swarm` showing a prod-backed skill detail page.
Note: default `/plugins` was not used because this PR head can request `sort=recommended`, which requires matching backend code that is not deployed to prod yet.
- Rendered generic admin one-off email with sample title/body/action content.
- Confirmed Plugin Inspector findings email renders without the removed ClawHub CTA button.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.