Record the ClawHub listing as live and correct its blocker note

docs/agent-skill.md still described the ClawHub surface as blocked: 1.0.3
and 1.0.4 stuck in pending.publication, with an instruction not to bump the
skill version until openclaw/clawhub#3643 resolved. The registry disagrees.
1.0.5, submitted by the clawhub job during the 0.39.0 release, is public:
clawhub search returns the row, and the public API reports tags.latest
1.0.5 with a single published version, which is also how the two earlier
submissions are shown never to have gone public. They were bypassed by the
next submission rather than recovered, and the pipeline issue stays open.

The note now says to read the catalog rather than the job log, since a
green job proves only a submission. It also records that the job fires on a
published release alone, so the 1.0.6 bump that landed after 0.39.0 reaches
ClawHub with the next release and must not be published by hand, and that
the listing carries MIT-0 where SKILL.md declares Apache-2.0, which the
publish command has no flag to set.

The awesome-openclaw entry loses its ClawHub prerequisite and stays
deferred on adoption alone: the listing reports no installs in 60 days.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PrJja6MnncVhyWnmXPN4GM

docs/agent-skill.md

@@ -54,10 +54,11 @@ Do these in order after the skill is on the default branch.
      brand-new skills ("give your skill time to mature and gain users before
      submitting"). Re-attempt after the skill has real installs and a
      release that ships it (0.38.0+).
-   - `VoltAgent/awesome-openclaw-skills`: DEFERRED. Entries are indexed via
-     clawskills.sh, so the skill must be published to ClawHub first, and the
-     list asks contributors not to submit skills "created 3 hours ago".
-     Re-attempt after the ClawHub publish plus visible adoption.
+   - `VoltAgent/awesome-openclaw-skills`: DEFERRED on adoption only. Entries
+     are indexed via clawskills.sh, and the ClawHub prerequisite in step 6 is
+     now met. The list still asks contributors not to submit skills "created
+     3 hours ago", and `clawhub search` reports 0 installs over 60 days.
+     Re-attempt once the listing shows real installs.
 5. **Claude community marketplace.** Form at
    [platform.claude.com/plugins/submit](https://platform.claude.com/plugins/submit)
    (individuals) or the claude.ai directory form (Team/Enterprise). Validate
@@ -68,20 +69,25 @@ Do these in order after the skill is on the default branch.
    official Anthropic marketplace is
    curated and has no application.
 6. **ClawHub.** `clawhub login` then `clawhub skill publish` from
-   `skills/remove-ai-watermarks/`. PUBLISHED 2026-09-07 (1.0.3) and
-   republished 2026-09-08 (1.0.4, identical content) — both sit in
-   `pending.publication` with CLEAN moderation, succeeded scan frameworks,
-   and null ClawScan / VirusTotal / Skillspector verdicts: a recurring
-   ClawHub pipeline defect tracked as openclaw/clawhub#3643 (prior reports:
-   #3624, #3466, #3351, #3284). Release-time publishing is automated through
-   the `clawhub` job in `distribute.yml` (see
-   [release-and-distribution.md](release-and-distribution.md)); do not bump
-   the version again to re-queue until the issue resolves, and re-check the
-   listing before any listing-dependent step such as the awesome-openclaw
-   submission. The public catalog already has an add-watermark
-   skill; this is the removal counterpart, framed as the user's own
-   content. ClawHub disallows deception, impersonation, and fake-engagement
-   install loops.
+   `skills/remove-ai-watermarks/`. LISTED 2026-09-09: version 1.0.5, submitted
+   by the `clawhub` job in `distribute.yml` during the 0.39.0 release, is
+   public. A green job proves only a submission, so read the catalog itself:
+   `clawhub search remove-ai-watermarks` returns the row and
+   `https://clawhub.ai/api/v1/skills/remove-ai-watermarks` reports
+   `tags.latest` 1.0.5 with a single published version. The earlier 1.0.3 and
+   1.0.4 submissions never became public and do not appear in that version
+   list, so they were bypassed rather than recovered; the pipeline defect that
+   held them, openclaw/clawhub#3643 (prior reports: #3624, #3466, #3351,
+   #3284), is still open. Release-time publishing is automated (see
+   [release-and-distribution.md](release-and-distribution.md)), and the job
+   fires only on a published GitHub Release: a skill version bumped after a
+   release, as 1.0.6 was, reaches ClawHub with the next one. Do not publish by
+   hand to close that gap. The listing records the license as MIT-0 while
+   `SKILL.md` declares Apache-2.0; `clawhub skill publish` has no license
+   flag, so correct it in the ClawHub listing itself. The public catalog
+   already has an add-watermark skill; this is the removal counterpart, framed
+   as the user's own content. ClawHub disallows deception, impersonation, and
+   fake-engagement install loops.
 7. **OpenAI ChatGPT / Codex plugin directory.** Skills-only plugins are a
    supported submission type at
    [platform.openai.com/plugins](https://platform.openai.com/plugins). This is