ntee-r1quest

Understand ntee-r1quest .ntd and .nts syntax, request keywords, macros (including `or` defaults), config behavior, and one-shot -p/-env/-ti execution. Use when explaining, reviewing, authoring, or fixing the syntax of individual R1Quest request scripts. To actually run/execute requests, use the r1quest-one-shot-runner skill instead.

Locate and execute ntee-r1quest .nts requests as one-shot commands. Use this whenever a user asks to run, call, trigger, or execute one or more named requests, referenced by name or path (with or without .nts) — a single request ("run google-api get-orders-by-id", "run folder-2/create-post") or several in sequence ("run folder-2/create-post then folder-2/update-post"), chained via a generated @joint file or per-step -env passing. This is THE skill for actually executing requests.

Generate ntee-r1quest request projects from Swagger/OpenAPI v3 YAML or JSON files. Use when asked to scan an OpenAPI spec and create .ntd data files plus .nts request files organized by project, HTTP method, and operation name.

Scan and edit an existing ntee-r1quest request root. Use when asked to inspect, update, or refactor .ntd data files and .nts request files in the current project.

Generate a ntee-r1quest GraphQL request project from a GraphQL schema file. Use when the user provides a schema path and asks to create or generate gql/graphql requests into an output directory or current CLI directory.

Generate GraphQL examples and request actions using ntee-r1quest .ntd and .nts files. Use when asked to create, convert, review, or run GraphQL queries or mutations in a R1Quest project.

Read and modify ntee-r1quest .r1qconfig.yaml configuration. Use when a user asks to view, add, or change R1Quest config such as the request root, AI adapter, socket path, custom editor suggestions, or custom AI commands.