indeed-jobs

{"keyword": "...", "location": "..."}

Relationship to

notte-browser

. This skill builds on the base CLI documented in the notte-browser skill. Load that skill for the full command reference, authentication handling, and security notes. This skill adds the explore-once -> generate -> self-test -> publish pipeline on top of it.

• One-off task ("scrape this page now") -> use

  notte-browser

  directly.
• Reusable artifact ("I'll run this across many inputs / on a schedule / from my backend") -> use this skill to build a Function.
• A built Function broke (site changed, returns empty) -> use notte-functions-doctor.

• Target site - a specific URL/platform, or only an objective ("track competitor prices").
• Output fields - the exact data to return (title, price, url, ...).
• Parameters - the business variables that change between runs (keyword, location, page count, category). These become

  run(...)

  arguments and Function invocation variables.
• Scale / recurrence - one input or many? On a schedule? This decides whether to offer

  notte functions schedule --function-id <function-id>

  at the end.

anything-api

https://anything.notte.cc/mcp

search

• A published Function that fits: use

  spec

  to read its variable schema, then

  run

  it, or

  notte functions fork --function-id <shared-function-id>

  it to own a copy. Report this to the user instead of building a duplicate - it saves the entire exploration cost.
• Nothing fits: continue to the gate below.

goto

notte sessions workflow-code --session-id "{session-id}" > built_function.py

instructions='...'

SyntaxError

from __future__ import annotations

response_format

PydanticUserError: Model is not fully defined

1. Give the exported

   run()

   its parameters - the export already defines

   run()

   , so shape that one rather than adding a second. Its parameters are the business variables from Phase 1, each with a sensible default; they become the Function's invocation variables.
2. Lift hardcoded inputs to parameters - the keyword, location, or page count you typed during exploration becomes

   run(keyword=..., location=...)

   . Endpoints, selectors, and field mappings stay hardcoded.
3. Confirm the response model - the exported Pydantic model is the output schema. Keep it tight and typed.
4. Stamp a health contract - a short, machine-readable comment block plus light runtime assertions describing what a correct result looks like (schema + sanity bounds, e.g. "at least 1 row", "price is numeric"). This is what makes a built Function repairable later by

   notte-functions-doctor

   .
5. Secrets, if the Function needs one - have the operator store them with

   notte functions secrets set NAME <value>

   , and read them from

   os.environ["NAME"]

   inside

   run()

   . Inspect with

   notte functions secrets list

   /

   get NAME

   , and remove with

   delete NAME

   . Never hardcode a secret or pass it as a run variable - run variables are recorded with the run.
6. Leave the trailing

   run()

   call alone - the export ends with one, and it is optional either way. The runtime invokes

   run()

   itself, so keeping or removing the call makes no difference. Don't spend a repair cycle on it.

1. Function ID and how to invoke it:
   bash

   # CLI
   notte functions run --function-id {function_id}
   
   # HTTP (from any backend / CI) - the Python SDK wraps this same endpoint
   curl -L -X POST "https://api.notte.cc/functions/{function_id}/runs/start" \
     -H "Authorization: Bearer $NOTTE_API_KEY" \
     -H "X-Notte-Api-Key: $NOTTE_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"function_id": "{function_id}", "variables": {"keyword": "AI engineer"}}'

2. Parameters (with defaults) and the returned schema.
3. Coverage gaps - fields that were sometimes missing, parameters not fully covered, account/permission limits. Never silently omit these.

• Before exploring - confirm the plan (Phase 1d).
• Before scheduling - confirm the cron cadence.
• Sensitive site actions (login, form submission, purchases, anything that writes) follow the

  notte-browser

  security notes and need explicit user confirmation.