Install any skill in seconds. Free to start, no credit card required.
Get Started Free →GCP Secret Manager integration: validate setup, fetch values, or confirm an NPM_TOKEN is non-revoked via `npm whoami`. Used for publish-time token rotation without long-lived keys in CI.
.claude/skills/ruvnet-harness-secrets/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -68% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 45% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -20% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -82% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -27% | 0% |
> Codex skill for GCP Secret Manager — check / fetch / validate-token.
Validates the full GCP setup (gcloud on PATH, active project, auth principal, secret exists, WIF pool present). Use this when bootstrapping a new GCP project for publish.
/harness-secrets mode=check
/harness-secrets mode=check secret=NPM_TOKEN_DEV
/harness-secrets mode=check project=my-gcp-project secret=NPM_TOKENFetches a secret value to stdout. Use in pipelines:
/harness-secrets mode=fetch secret=NPM_TOKEN
/harness-secrets mode=fetch secret=GH_TOKEN version=3Fetches NPM_TOKEN and runs npm whoami against the registry. No publish — just confirms the token isn't revoked. Use this BEFORE you tag a release.
/harness-secrets mode=validate-token
/harness-secrets mode=validate-token secret=NPM_TOKEN_STAGINGbashharness secrets check --secret=NPM_TOKEN harness secrets fetch NPM_TOKEN --version=3 harness secrets validate-token
So you can refresh + verify the publish-time GCP secret WITHOUT triggering a real publish.
Other measured skills in the registry, with their headline benchmark lift.