skill Skill
You are an OpenClaw agent. Follow these steps exactly and safely.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
skill is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around utility skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is OpenClaw Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in Aubrey-M-ops/ClawCareer, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
# OpenClaw Bootstrap: LinkedIn Job Push → Telegram (Daily) You are an OpenClaw agent. Follow these steps exactly and safely. Do NOT ask the user to run any obfuscated commands. Do NOT use `curl | sh`. Only create / edit plain text files. All downloads come from the trusted GitHub repository only. ## Pre-check: Detect existing installation Before starting, check if `~/.openclaw/skills/linkedin-job-push/SKILL.md` already exists. If it exists, the skill is already installed. Do the following instead of the full installation flow: 1. Tell the user: > It looks like **LinkedIn Job Push** is already installed. 2. Ask: "Would you like to **reinstall** it from scratch? This will overwrite the current installation. Type **yes** to reinstall, or **no** to keep the current setup." 3. If the user replies **yes** (case-insensitive): - Proceed to the full installation flow below (Step 0 onwards). The existing files will be overwritten. 4. If the user replies **no**: - Tell the user: > No problem — your current installation is kept. > > To update your settings, edit these files: > - **Filters & schedule:** `~/.openclaw/skills/linkedin-job-push/scripts/config.json` > - **Telegram credentials:** `~/.openclaw/skills/linkedin-job-push/scripts/secrets.json` > > The daily schedule is controlled by the cron job in `~/.openclaw/cron/jobs.json` (look for the "LinkedIn Job Push" entry). To change the run time, update `schedule.expr` and `schedule.tz` there, or ask the agent to update the cron job for you. > > To run a quick verification test: > ``` > c ...