Interview Agenda Builder

Use this skill for routine recruiting operations work when the user asks to build an interview agenda.

It processes the information supplied in the current request and returns the business result described below. It does not require credentials or access to private files.

Input

Field: interview_plan

Role-focused topic plan prepared for an interview handoff.

Accepted value: object with candidate_id, matched_required, missing_required, topics.

Output

Field: agenda_artifact

Return a concise agenda artifact for the user's current request in the requested output field. The returned value is a object with agenda_id, candidate_id, markdown.

Example Request

Use the supplied interview_plan to build an interview agenda.
Return the result in agenda_artifact.

Bundled execution

Use Python 3.10 or newer to run this operation from the installed package directory. Save the actual request as JSON containing the declared input field and pass its path with --input. The bundled example demonstrates the input shape.

python scripts/run.py --input examples/request.json --output-dir ./workspace

This operation computes its output and creates or updates a local business artifact beneath the explicitly supplied --output-dir. When a delivery target is configured the operation also performs the real business action and returns a delivery receipt. Effect: local_interview_agenda_render.

Report the actual command output and, when present, its effect receipt. A nonzero exit means the operation failed. This package executes only its declared operation.

The implementation is scripts/operation.py, input/output validation is scripts/validation.py, and role configuration is scripts/config.json. All Python dependencies are from the standard library. Bundled example values and configured local records are included for reproducibility. Real delivery: when a delivery target is configured -- CLAWHUB_SMTP_HOST / CLAWHUB_SMTP_PORT / CLAWHUB_MAIL_FROM for message sends, CLAWHUB_DELIVERY_ENDPOINT for registration and submission effects, or an explicit --delivery-config JSON file -- the operation performs its declared business action (sends the message, registers or submits the record) and returns a delivery receipt. Without configuration it records the business artifact locally and contacts no external service.