surface-define
Skill4 starsChanged 2 months agoApache-2.0View on GitHub
Define a new public career surface, or rethink the positioning intent of an existing one — a profile on a platform (LinkedIn, Upwork, or one this repo doesn't ship a definition for), or a free-form surface (portfolio, personal site, GitHub README, speaker bio). Researches an unknown platform, works out with the candidate what the surface should emphasize, and writes data/surfaces/<name>/context.md. Use when the candidate wants a surface they don't have yet, or wants to change what an existing one communicates (not just refresh it with new evidence).
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agents.mdcCursor rule
- add-from-urlSkill
- boardSkill
- communication-logSkill
- cover-letterSkill
- cv-reviewSkill
- cv-targetedSkill
- cv-universalSkill
- engagement-fitmentSkill
- fitmentSkill
- interview-prepSkill
- linkedin-searchSkill
- onboardSkill
- pitchSkill
- prioritizeSkill
- reconcileSkill
- scoutSkill
- update-surfaceSkill
- workspace-validateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Read and follow playbooks/surface-define.md in full.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read and follow playbooks/surface-define.md in full. It is the single source of truth for this
skill — don't duplicate its instructions here, don't skip steps because they seem implied.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.