Skill Extraction

Pull skills out of a job description or CV and sort them into technical skills, soft skills, tools, certifications and languages.

Pay by wallet (x402) skill-extract

Example

Example answer
{
  "tools": [],
  "languages": [],
  "soft_skills": [],
  "certifications": [],
  "technical_skills": [],
  "seniority_signals": [],
  "total_skills_found": 0,
  "experience_levels_mentioned": []
}

Inputs

FieldTypeRequiredWhat it is
textstringYesJob description or CV text

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
toolsarrayUsually (present for most inputs)
languagesarrayAlways (present in every successful answer)
soft_skillsarrayUsually (present for most inputs)
certificationsarrayUsually (present for most inputs)
technical_skillsarrayAlways (present in every successful answer)
seniority_signalsarrayUsually (present for most inputs)
total_skills_foundintegerAlways (present in every successful answer)
experience_levels_mentionedarrayUsually (present for most inputs)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "skill-extract",
    "inputs": {
      "text": "Senior backend engineer with 6 years building Python and TypeScript services on AWS and Kubernetes. Day-to-day tools are Docker, Git and Terraform. AWS Certified Solutions Architect. Known for clear written communication and mentoring juniors. Fluent in Swedish and English."
    },
    "max_price_cents": 3
  }'

Limitations

  • Skill categories can differ from industry taxonomies

    AI-powered skill extraction — may categorise broad competencies differently than specific industry taxonomies (e.g., ESCO, O*NET)

    What to do instead: Map extracted skills to your target taxonomy (ESCO, O*NET) as a post-processing step for HR system integration