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.
Demographic fields — age, gender, nationality, ethnicity — are deliberately excluded from the schema to comply with the EU AI Act and to reduce bias in automated screening.
Schema
Protocol version this profile conforms to. Current value:
"0.1.0".Your professional name as you want it presented to agents and employers.
Your current or most recent professional title (e.g.
"Senior Software Engineer", "Executive Chef").Your seniority level. One of:
entry, junior, mid, senior, lead, manager, director, executive.Total years of professional experience.
Current availability for new opportunities. One of:
immediately, in_2_weeks, in_4_weeks, in_8_weeks, not_looking.Top-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.Your 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, equipment, software, or platforms used in professional work — for example
"Kubernetes", "AWS", "Docker".Professional certifications or licenses — for example
"AWS Solutions Architect Associate", "CDL-A", "ServSafe".Niche areas of deep expertise — for example
"Event-Driven Architecture", "API Gateway Design".Languages you speak professionally.
Highest relevant education or training — for example
"BSc Computer Science, UC Berkeley".A 2–3 sentence professional summary. Maximum 1000 characters.
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
Based on the sample card in the repository: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 |