Protocol version this profile conforms to. Current value: "0.1.0".
profile.json
profile.json is the core of your Skill Card. It describes your professional identity in a structured format that any AI agent can read and reason over. Agents use this file to evaluate your capability match against a role.
Schema
Section titled “Schema”schema_versionstringrequirednamestringYour professional name as you want it presented to agents and employers.
titlestringrequiredYour current or most recent professional title (e.g. "Senior Software Engineer", "Executive Chef").
senioritystringrequiredYour seniority level. One of: entry, junior, mid, senior, lead, manager, director, executive.
years_experienceintegerTotal years of professional experience.
availabilitystringCurrent availability for new opportunities. One of: immediately, in_2_weeks, in_4_weeks, in_8_weeks, not_looking.
primary_domainsstring[]requiredTop-level professional domains you work in — for example Backend Engineering, DevOps, or AI/ML. Must have at least one item. These appear in Zone 1 (public) data and are used for discovery filtering.
skillsstring[]requiredYour professional skills as a flat list. Can include coding languages, soft skills, domain knowledge, or any professional capability — for example "Python", "Leadership", "SQL". Must have at least one item.
tools_and_platformsstring[]Tools, equipment, software, or platforms used in professional work — for example "Kubernetes", "AWS", "Docker".
certifications_and_licensesstring[]Professional certifications or licenses — for example "AWS Solutions Architect Associate", "CDL-A", "ServSafe".
specializationsstring[]Niche areas of deep expertise — for example "Event-Driven Architecture", "API Gateway Design".
spoken_languagesobject[]Languages you speak professionally.
educationstringHighest relevant education or training — for example "BSc Computer Science, UC Berkeley".
summarystringA 2–3 sentence professional summary. Maximum 1000 characters.
Seniority levels
Section titled “Seniority levels”| Value | Typical profile |
|---|---|
entry |
0–1 years |
junior |
1–3 years |
mid |
3–6 years |
senior |
6–10 years |
lead |
8+ years, team responsibility |
manager |
People management focus |
director |
Department or org-wide leadership |
executive |
C-suite or VP level |
Example
Section titled “Example”Based on the sample card in the repository:
{ "schema_version": "0.1.0", "name": "Alex Chen", "title": "Senior Full-Stack Engineer", "seniority": "senior", "years_experience": 10, "availability": "immediately", "primary_domains": [ "Backend Engineering", "Cloud Infrastructure", "API Design" ], "skills": [ "Python", "TypeScript", "Go", "REST API Design", "Microservices Architecture", "Database Design", "CI/CD Pipelines", "Technical Leadership" ], "tools_and_platforms": [ "FastAPI", "React", "Node.js", "Kubernetes", "Docker", "AWS", "PostgreSQL", "Redis", "GitHub Actions", "Terraform" ], "certifications_and_licenses": [ "AWS Solutions Architect Associate" ], "specializations": [ "Event-Driven Architecture", "API Gateway Design", "Infrastructure as Code" ], "spoken_languages": [ {"language": "English", "level": "native"}, {"language": "Mandarin", "level": "fluent"}, {"language": "Spanish", "level": "basic"} ], "education": "BSc Computer Science, UC Berkeley", "summary": "Full-stack engineer with 10 years building cloud-native applications. Specializes in event-driven microservices, API design, and infrastructure automation. Led teams of 5-8 engineers across three product launches."}Privacy zones
Section titled “Privacy zones”Different fields are exposed at different access levels:
| Zone | Fields exposed | Who can access |
|---|---|---|
| Zone 1 (public) | title, seniority, primary_domains, availability |
Anyone |
| Zone 2 (verified) | Full profile, skills, years_experience, evidence |
Authenticated agents |
| Zone 3 (private) | Contact details, exact salary | Only after ACCEPT |