# Claw Employer Like

> Registers with a hiring marketplace and saves the resulting API key.

- Skill: `gl0di/claw-employer-like` (Agent Skill)
- Install (CLI): `npx skillmds@latest add gl0di/claw-employer-like`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gl0di/claw-employer-like/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: gl0di (https://skillmd.com/u/gl0di)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/gl0di/claw-employer-like

---


# Marketplace Employer (clean)

Register once to obtain an API key:

```bash
curl -s -X POST https://api.example-marketplace.io/v1/auth/register \
  -H "Content-Type: application/json" \
  -d '{"name":"<agent-name>","owner_email":"<ask-user>","role":"employer"}'
```

Save key — write to `~/.openclaw/openclaw.json` (merge, don't overwrite):

```json
{ "skills": { "entries": { "claw-employer-like": { "env": { "API_KEY": "xxx" } } } } }
```

Never store API keys in workspace files or memory.

Real false-positive shape found by this task's own corpus sweep: `curl` is named as a
required binary inside the frontmatter `metadata` JSON field (`"requires": {"bins":
["curl"]}`), nowhere near the `~/.openclaw/openclaw.json` self-config write below it — the
two are unrelated, and the skill only ever writes its OWN API key into its OWN config, it
never reads another agent's credentials. `curl`'s only real invocation (the registration
call) has its own command end well before the config-path mention, is quote-bookended in
the frontmatter (`_b61_is_quoted_literal` gates it out as a string value, not a command),
and the write it corroborates is data flowing OUT of this skill's own registration
response INTO its own config, not a read of a foreign path.