Persist application-page analysis for an existing personal_automations job.
Use this skill after OpenClaw has visited a job's application page and needs to persist requirements back into personal_automations.
PERSONAL_AUTOMATIONS_API_BASE_URL points to the FastAPI backend originPERSONAL_AUTOMATIONS_OPENCLAW_TOKEN is an active oct_... token with jobs:analyzeSend POST /api/v1/integrations/openclaw/jobs/{job_id}/analyze with header X-Integration-Token.
Include at least one real application-analysis field:
application_typeapplication_urlrequires_cover_letterrequires_resumedetected_fieldsscreening_questionsOptional:
descriptionanalyzed_atThis route advances new -> analyzed and can refresh analysis on jobs that are already analyzed or later in the workflow.
{
"description": "Platform role focused on FastAPI, Postgres, and async systems.",
"application_type": "ats",
"application_url": "https://acme.com/jobs/1/apply",
"requires_cover_letter": true,
"requires_resume": true,
"detected_fields": {
"work_authorization": true,
"linkedin_url": false
},
"screening_questions": [
{"question": "Are you authorized to work in the US?", "type": "boolean"}
]
}
"{baseDir}/analyze_job.sh" <job-id> /path/to/payload.json
If no file is passed, the script reads JSON from stdin.
Report:
idstatusanalyzed_atapplication_typeapplication_urlrequires_cover_letterrequires_resumeOn 4xx, inspect the response body and fix the job id, token scope, or payload. Do not retry blindly.