@emergentmethods/asknews-cli 0.1.0

package/package.json

@@ -0,0 +1,79 @@
+{
+  "name": "@emergentmethods/asknews-cli",
+  "version": "0.1.0",
+  "description": "The official AskNews CLI for humans, automation, and agents",
+  "type": "module",
+  "license": "MIT",
+  "author": "Emergent Methods <contact@emergentmethods.ai>",
+  "homepage": "https://docs.asknews.app/cli",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/emergentmethods/asknews-cli.git"
+  },
+  "bugs": "https://github.com/emergentmethods/asknews-cli/issues",
+  "keywords": [
+    "asknews",
+    "news",
+    "cli",
+    "deepnews",
+    "research",
+    "agents",
+    "openapi"
+  ],
+  "bin": {
+    "asknews": "./dist/bin.js"
+  },
+  "files": [
+    "dist/",
+    "skills/",
+    "scripts/postinstall.mjs"
+  ],
+  "engines": {
+    "node": ">=22.15"
+  },
+  "packageManager": "pnpm@10.11.0",
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "pnpm generate && pnpm build:bundle",
+    "build:bundle": "tsx scripts/build.ts",
+    "check": "pnpm lint && pnpm typecheck && pnpm test:coverage",
+    "dev": "tsx src/bin.ts",
+    "generate": "pnpm generate:openapi && pnpm generate:docs",
+    "generate:docs": "tsx scripts/generate-docs.ts",
+    "generate:openapi": "tsx scripts/generate-openapi.ts",
+    "lint": "biome check .",
+    "lint:fix": "biome check --write .",
+    "postinstall": "node scripts/postinstall.mjs",
+    "package:tarball": "tsx scripts/package-tarball.ts",
+    "sync:docs": "tsx scripts/sync-docs-site.ts",
+    "sync:docs:check": "tsx scripts/sync-docs-site.ts --check",
+    "sync:openapi": "tsx scripts/sync-openapi.ts",
+    "sync:openapi:check": "tsx scripts/sync-openapi.ts --check",
+    "test": "vitest run",
+    "test:coverage": "vitest run --coverage",
+    "test:live": "ASKNEWS_LIVE_TESTS=1 vitest run test/live",
+    "typecheck": "tsc --noEmit"
+  },
+  "dependencies": {
+    "@clack/prompts": "1.6.0",
+    "chalk": "5.6.2",
+    "cli-table3": "0.6.5",
+    "commander": "14.0.3",
+    "terminal-link": "^5.0.0",
+    "yaml": "2.8.3",
+    "zod": "3.25.76"
+  },
+  "devDependencies": {
+    "@biomejs/biome": "2.5.0",
+    "@types/node": "22.19.1",
+    "@vitest/coverage-v8": "4.1.9",
+    "esbuild": "0.28.1",
+    "fast-check": "4.8.0",
+    "openapi-types": "12.1.3",
+    "tsx": "4.22.4",
+    "typescript": "5.9.3",
+    "vitest": "4.1.9"
+  }
+}

package/scripts/postinstall.mjs

@@ -0,0 +1,26 @@
+import { cpSync, existsSync, mkdirSync } from "node:fs";
+import { homedir } from "node:os";
+import { dirname, join, resolve } from "node:path";
+import { fileURLToPath } from "node:url";
+
+if (process.env.ASKNEWS_NO_AGENT_SKILLS !== "1") {
+  const packageRoot = resolve(dirname(fileURLToPath(import.meta.url)), "..");
+  const source = resolve(packageRoot, "skills/asknews-cli");
+  const agentHome =
+    process.env.ASKNEWS_AGENT_HOME || process.env.npm_config_asknews_agent_home || homedir();
+  if (existsSync(source) && !existsSync(resolve(packageRoot, ".git"))) {
+    const agentRoots = [join(agentHome, ".agents")];
+    const claudeRoot = join(agentHome, ".claude");
+    if (existsSync(claudeRoot)) agentRoots.push(claudeRoot);
+    for (const agentRoot of agentRoots) {
+      const target = join(agentRoot, "skills", "asknews-cli");
+      try {
+        mkdirSync(dirname(target), { recursive: true });
+        cpSync(source, target, { recursive: true, force: true });
+      } catch (error) {
+        const message = error instanceof Error ? error.message : String(error);
+        process.stderr.write(`AskNews agent skill setup skipped for ${agentRoot}: ${message}\n`);
+      }
+    }
+  }
+}

package/skills/asknews-cli/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: asknews-cli
+description: Use the AskNews CLI for current or historical news retrieval, story tracking, multi-source DeepNews research, web/Reddit/Wikipedia search, alerts, and any customer-facing AskNews API operation. Use when an agent needs sourced real-world information, news context, structured AskNews data, or safe AskNews automation.
+---
+
+# AskNews CLI
+
+Use `asknews` instead of constructing HTTP requests. The CLI handles authentication, schema-derived
+parameters, API errors, output formats, and mutation safeguards.
+
+## Workflow
+
+1. Verify availability with `asknews --version`. If it is missing, tell the user how to install it;
+   do not invent an API fallback.
+2. Check credentials with `asknews auth status --offline --output json`. Never display credentials.
+3. Select the narrowest command family that answers the request.
+4. For unfamiliar or advanced options, run that command's `--help` before execution. The installed
+   help is authoritative because it is generated from the current OpenAPI schema.
+5. Start with a small result set, inspect structured output, then broaden only when needed.
+6. Report the answer with dates and source provenance. Distinguish retrieved facts from your own
+   synthesis.
+
+## Select the command
+
+| Need | Use |
+| --- | --- |
+| Individual current or historical articles | `asknews news search` |
+| Clustered narratives and evolving events | `asknews stories list`, then `stories get` |
+| A synthesized answer across multiple sources | `asknews research` |
+| Live web, Reddit, or Wikipedia context | `asknews web`, `asknews reddit`, `asknews wiki` |
+| Existing monitoring configuration | `asknews alerts` |
+| A less common public API capability | `asknews api list`, then a generated command |
+| An API path with no generated command | `asknews request` as a last resort |
+
+Use article search when the user needs evidence or a source set. Use stories when they need the
+shape and development of an event. Use DeepNews only when synthesis is requested or materially
+useful; it is slower and potentially more expensive than retrieval.
+
+## Output and context discipline
+
+- Use `--output json` for agent inspection and transformation.
+- Use `--output jsonl` with `--stream` when incremental DeepNews events are useful.
+- Use human/table output only for a person reading the terminal.
+- Result data is on stdout; diagnostics are on stderr. Do not parse diagnostics as data.
+- Begin with `--limit 5` for article or story discovery unless the user requests broader coverage.
+- Prefer exact UTC timestamps or explicit lookback windows for time-sensitive work.
+- Preserve source names, URLs, publication dates, article/story IDs, and citations needed to audit
+  the answer. Do not paste the entire raw response when a concise synthesis is enough.
+- If results are empty or weak, say so; adjust one search dimension at a time rather than silently
+  presenting unrelated results.
+
+## Discovery
+
+```bash
+asknews <command> --help
+asknews api list --output json
+asknews api list --tag news --output json
+asknews api list --safety high-cost --output json
+asknews api <group> <operation> --help
+```
+
+Generated flags use kebab-case: OpenAPI `start_timestamp` becomes `--start-timestamp`. Use
+schema-derived flags first and repeat array options when documented. Use `--param name=value` only
+as an escape hatch.
+
+Read [references/task-recipes.md](references/task-recipes.md) when the task needs advanced news
+filters, research tuning, source-specific search, generated API operations, or mutations. Do not
+load it for a straightforward search.
+
+For exact command arguments and options, read
+[references/commands/index.md](references/commands/index.md), then load only the relevant route
+reference. These files are generated from the same Commander/OpenAPI metadata as `--help`.
+
+## Authentication, cost, and safety
+
+- Prefer OAuth for people and `ASKNEWS_API_KEY` for CI/agents. Avoid `--api-key` because command-line
+  arguments can appear in process listings and shell history.
+- If credentials are absent, ask the user to run `asknews auth login` or configure
+  `ASKNEWS_API_KEY`; never request that they paste a secret into chat.
+- Treat historical search, DeepNews, web search, graph, forecast, and explicitly labeled high-cost
+  operations as billable. Keep scope narrow and do not automatically retry chargeable failures.
+- Read-only retrieval may proceed when it directly answers the request. Creating, updating,
+  deleting, sending, running, or triggering a resource requires clear user authorization.
+- Before a mutation, inspect operation help, summarize the intended effect, and use `--yes` only
+  after authorization. Never infer permission from access to credentials.
+
+## Failure handling
+
+- Unknown option or validation error: inspect the exact command's `--help`; do not guess enum values.
+- `401`: authentication is absent or expired; recheck `auth status`.
+- `403`: the account or plan may not permit the operation; do not evade the restriction.
+- `429`: report rate limiting and respect retry guidance; do not loop aggressively.
+- Timeout or transient server error: retry read-only work at most once unless the user asks for
+  persistence. Do not automatically retry mutations or expensive research.

package/skills/asknews-cli/references/commands/alerts.md

@@ -0,0 +1,135 @@
+# alerts
+
+Create and manage AskNews alerts
+
+## Commands
+
+### `asknews alerts list`
+
+List alerts
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--user-id <value>` | The ID of the user to get alerts for [query, string, optional] |
+| `--page <value>` | The page number to get [query, integer, optional, default: 1] |
+| `--per-page <value>` | The number of items per page [query, integer, optional, default: 10] |
+| `--all [boolean]` | Whether to get all the alerts [query, boolean, optional, default: false] |
+| `--include-deleted [boolean]` | Whether to include soft-deleted alerts [query, boolean, optional, default: false] |
+
+**Examples:**
+
+```bash
+asknews alerts list --output json
+```
+
+### `asknews alerts get <alert-id>`
+
+Get an alert
+
+**Arguments:**
+
+| Argument | Description |
+| --- | --- |
+| `<alert-id>` | alert UUID |
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--user-id <value>` | The ID of the user to get logs for [query, string, optional] |
+
+### `asknews alerts create`
+
+Create an alert
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--body <json-or-file>` | complete alert JSON or @file.json |
+| `-y, --yes` | confirm alert create |
+| `--query <value>` | The query to run for retrieving information from sources, and for checking the alert. If you have defined one or more reports, specify each report's individual query in the report prompt. [body, string\|null, optional] |
+| `--sources <value>` | The sources to use for retrieving information related to the alert query. Available sources are: AskNewsSource, TelegramSource, BlueskySource, WebSource, DeepNewsSource [body, array\|null, optional] |
+| `--alert-type <value>` | The type of alert. If specified, overrides `repeat` and `always_trigger`. 'AlwaysAlertWhen': trigger alert actions any time the alert query is satisfied (`repeat=True`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'AlertOnceIf': trigger alert actions when the alert query is satisfied and then disable the alert (`repeat=False`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'ReportAbout': always trigger alert actions according to cron schedule and write a report (`repeat=True`, `always_trigger=True`). Defaults to using DeepNews for the report unless specified. [body, string\|null, optional] Choices: AlwaysAlertWhen, AlertOnceIf, ReportAbout. |
+| `--model <value>` | The model that is used to check if the alert conditions are satisfied by sources (this is not the same as the model used to write the report.)Defaults to gpt-4o. [body, string, optional, default: "gpt-4o"] Choices: meta-llama/Meta-Llama-3.1-8B-Instruct, gpt-4o-mini, gpt-5-mini, gpt-5-nano, gpt-4o, o3-mini, meta-llama/Meta-Llama-3.3-70B-Instruct, gpt-4.1-2025-04-14, gpt-4.1-nano-2025-04-14, gpt-4.1-mini-2025-04-14. |
+| `--cron <value>` | How often or when to check sources for this alert, specified as a cron expression. Examples: '0 * * * *' (hourly), '0 9 * * *' (daily at 9am), '0 9 * * 1' (Mondays at 9am). See https://crontab.run/ for more examples. [body, string, required] |
+| `--triggers <value>` | body array<object> value [body, array<object>, required] |
+| `--always-trigger [boolean]` | Whether to always trigger the actions when sources are scanned. This skips the check for if the alert conditions are satisfied and run triggers immediately. Defaults to False. [body, boolean, optional, default: false] |
+| `--repeat [boolean]` | Whether to repeat the alert. Default is True. If False, the alert will be disabled after it triggers once. [body, boolean, optional, default: true] |
+| `--active [boolean]` | Whether the alert is active or not. Default is True. [body, boolean, optional, default: true] |
+| `--expires-at <value>` | The expiration date for the alert. Default is None. If set, the alert will be disabled after this date. [body, string\|null, optional] |
+| `--report <value>` | Configuration for generating a written report when the alert triggers. If report is a list, the individual reports will be concatenated into one report in the order they are defined. If not specified, no report is generated. Use ReportRequest(identifier='deepnews', ...) for DeepNews reports.Use ReportRequest(...) or ReportRequest(identifier='legacy', ...) for legacy reports (DEPRECATED). Requests without identifier default to 'deepnews'. Only DeepNews reports can be used in list. [body, array\|null, optional] |
+| `--title <value>` | The title of the alert. If not provided, no title will be used. [body, string\|null, optional] |
+| `--share-link <value>` | The newsplunker share link to update when the alert triggers. [body, string\|null, optional] |
+
+### `asknews alerts update <alert-id>`
+
+Update an alert
+
+**Arguments:**
+
+| Argument | Description |
+| --- | --- |
+| `<alert-id>` | alert UUID |
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--body <json-or-file>` | complete alert JSON or @file.json |
+| `-y, --yes` | confirm alert update |
+| `--query <value>` | The query to run for retrieving information from sources, and for checking the alert. If you have defined one or more reports, specify each report's individual query in the report prompt. [body, string\|null, optional] |
+| `--sources <value>` | The sources to use for retrieving information related to the alert query. Available sources are: AskNewsSource, TelegramSource, BlueskySource, WebSource, DeepNewsSource [body, array\|null, optional] |
+| `--alert-type <value>` | The type of alert. If specified, overrides `repeat` and `always_trigger`. 'AlwaysAlertWhen': trigger alert actions any time the alert query is satisfied (`repeat=True`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'AlertOnceIf': trigger alert actions when the alert query is satisfied and then disable the alert (`repeat=False`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'ReportAbout': always trigger alert actions according to cron schedule and write a report (`repeat=True`, `always_trigger=True`). Defaults to using DeepNews for the report unless specified. [body, string\|null, optional] Choices: AlwaysAlertWhen, AlertOnceIf, ReportAbout. |
+| `--model <value>` | The model that is used to check if the alert conditions are satisfied by sources (this is not the same as the model used to write the report.) [body, string\|null, optional] Choices: meta-llama/Meta-Llama-3.1-8B-Instruct, gpt-4o-mini, gpt-5-mini, gpt-5-nano, gpt-4o, o3-mini, meta-llama/Meta-Llama-3.3-70B-Instruct, gpt-4.1-2025-04-14, gpt-4.1-nano-2025-04-14, gpt-4.1-mini-2025-04-14. |
+| `--cron <value>` | How often or when to check sources for this alert, specified as a cron expression. Examples: '0 * * * *' (hourly), '0 9 * * *' (daily at 9am), '0 9 * * 1' (Mondays at 9am). See https://crontab.run/ for more examples. [body, string\|null, optional] |
+| `--triggers <value>` | Configuration for actions to trigger for the alert. Available actions are: WebhookAction, EmailAction, ResendBroadcastAction, GoogleDocsAction [body, array\|null, optional] |
+| `--always-trigger [boolean]` | Whether to always trigger the actions when sources are scanned. This skips the check for if the alert conditions are satisfied and run triggers immediately. Defaults to False. [body, boolean\|null, optional] |
+| `--repeat [boolean]` | Whether to repeat the alert. Default is True. If False, the alert will be disabled after it triggers once. [body, boolean\|null, optional] |
+| `--active [boolean]` | Whether the alert is active or not. Default is True. [body, boolean\|null, optional] |
+| `--expires-at <value>` | The expiration date for the alert. Default is None. If set, the alert will be disabled after this date. [body, string\|null, optional] |
+| `--report <value>` | Configuration for generating a written report when the alert triggers. If report is a list, the individual reports will be concatenated into one report in the order they are defined. If not specified, no report is generated. Use ReportRequest(identifier='deepnews', ...) for DeepNews reports.Use ReportRequest(...) or ReportRequest(identifier='legacy', ...) for legacy reports (DEPRECATED). Requests without identifier default to 'deepnews'. Only DeepNews reports can be used in list. [body, object\|array\|null, optional] |
+| `--title <value>` | The title of the alert. If not provided, no title will be used. [body, string\|null, optional] |
+| `--share-link <value>` | The newsplunker share link to update when the alert triggers. [body, string\|null, optional] |
+
+### `asknews alerts delete <alert-id>`
+
+Delete an alert
+
+**Arguments:**
+
+| Argument | Description |
+| --- | --- |
+| `<alert-id>` | alert UUID |
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `-y, --yes` | confirm alert deletion |
+
+### `asknews alerts run <alert-id>`
+
+Run an existing alert
+
+**Arguments:**
+
+| Argument | Description |
+| --- | --- |
+| `<alert-id>` | alert UUID |
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `-y, --yes` | confirm billable alert run |
+| `--user-id <value>` | The ID of the user to get logs for [query, string, optional] |
+| `--is-test [boolean]` | Whether this is a test run [query, boolean, optional, default: false] |
+
+## Global options
+
+All commands support `--output human|table|json|jsonl|yaml`, `--json`, API/auth URL
+overrides, request timeout, and color control. Result data is written to stdout; diagnostics
+are written to stderr.

package/skills/asknews-cli/references/commands/api-alerts.md

@@ -0,0 +1,186 @@
+# api alerts
+
+Generated from AskNews API 0.24.95.
+
+## Operations
+
+### `asknews api alerts create-alert`
+
+Create an alert.
+
+- Request: `POST /v1/chat/alerts`
+- Operation ID: `create_alert`
+- Safety: `mutating`
+
+**Request body fields:**
+
+| Option | Type | Required | Description |
+| --- | --- | --- | --- |
+| `--query` | string or null | no | The query to run for retrieving information from sources, and for checking the alert. If you have defined one or more reports, specify each report's individual query in the report prompt. |
+| `--sources` | array or null | no | The sources to use for retrieving information related to the alert query. Available sources are: AskNewsSource, TelegramSource, BlueskySource, WebSource, DeepNewsSource |
+| `--alert-type` | string or null | no | The type of alert. If specified, overrides `repeat` and `always_trigger`. 'AlwaysAlertWhen': trigger alert actions any time the alert query is satisfied (`repeat=True`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'AlertOnceIf': trigger alert actions when the alert query is satisfied and then disable the alert (`repeat=False`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'ReportAbout': always trigger alert actions according to cron schedule and write a report (`repeat=True`, `always_trigger=True`). Defaults to using DeepNews for the report unless specified. |
+| `--model` | string | no | The model that is used to check if the alert conditions are satisfied by sources (this is not the same as the model used to write the report.)Defaults to gpt-4o. Choices: meta-llama/Meta-Llama-3.1-8B-Instruct, gpt-4o-mini, gpt-5-mini, gpt-5-nano, gpt-4o, o3-mini, meta-llama/Meta-Llama-3.3-70B-Instruct, gpt-4.1-2025-04-14, gpt-4.1-nano-2025-04-14, gpt-4.1-mini-2025-04-14. Default: `"gpt-4o"`. |
+| `--cron` | string | yes | How often or when to check sources for this alert, specified as a cron expression. Examples: '0 * * * *' (hourly), '0 9 * * *' (daily at 9am), '0 9 * * 1' (Mondays at 9am). See https://crontab.run/ for more examples. |
+| `--triggers` | array<object> | yes |  |
+| `--always-trigger` | boolean | no | Whether to always trigger the actions when sources are scanned. This skips the check for if the alert conditions are satisfied and run triggers immediately. Defaults to False. Default: `false`. |
+| `--repeat` | boolean | no | Whether to repeat the alert. Default is True. If False, the alert will be disabled after it triggers once. Default: `true`. |
+| `--active` | boolean | no | Whether the alert is active or not. Default is True. Default: `true`. |
+| `--expires-at` | string or null | no | The expiration date for the alert. Default is None. If set, the alert will be disabled after this date. |
+| `--report` | array or null | no | Configuration for generating a written report when the alert triggers. If report is a list, the individual reports will be concatenated into one report in the order they are defined. If not specified, no report is generated. Use ReportRequest(identifier='deepnews', ...) for DeepNews reports.Use ReportRequest(...) or ReportRequest(identifier='legacy', ...) for legacy reports (DEPRECATED). Requests without identifier default to 'deepnews'. Only DeepNews reports can be used in list. |
+| `--title` | string or null | no | The title of the alert. If not provided, no title will be used. |
+| `--share-link` | string or null | no | The newsplunker share link to update when the alert triggers. |
+
+Use direct kebab-case body options, `--body '{...}'`, or `--body @request.json`.
+Direct body options override values supplied through `--body`.
+
+This operation requires confirmation and `--yes` in non-interactive use.
+
+### `asknews api alerts delete-alert`
+
+Delete an alert.
+
+- Request: `DELETE /v1/chat/alerts/{alert_id}`
+- Operation ID: `delete_alert`
+- Safety: `mutating`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--alert-id` | The alert ID Location: path. Type: string. Required. Format: uuid. |
+
+This operation requires confirmation and `--yes` in non-interactive use.
+
+### `asknews api alerts get-alert`
+
+Get an alert.
+
+- Request: `GET /v1/chat/alerts/{alert_id}`
+- Operation ID: `get_alert`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--alert-id` | The alert ID Location: path. Type: string. Required. Format: uuid. |
+| `--user-id` | The ID of the user to get logs for Location: query. Type: string. Optional. |
+
+### `asknews api alerts get-alert-logs`
+
+Get alert logs.
+
+- Request: `GET /v1/chat/alerts/{alert_id}/logs`
+- Operation ID: `get_alert_logs`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--alert-id` | The alert ID Location: path. Type: string. Required. Format: uuid. |
+| `--user-id` | The ID of the user to get logs for Location: query. Type: string. Optional. |
+| `--page` | The page number to get Location: query. Type: integer. Optional. Default: `1`. |
+| `--per-page` | The number of items per page Location: query. Type: integer. Optional. Default: `10`. |
+| `--all` | Whether to get all the alert logs Location: query. Type: boolean. Optional. Default: `false`. |
+| `--start-timestamp` | Timestamp to start search from Location: query. Type: string. Optional. |
+| `--end-timestamp` | Timestamp to end search at Location: query. Type: string. Optional. |
+
+### `asknews api alerts get-alerts`
+
+Get all created alerts.
+
+- Request: `GET /v1/chat/alerts`
+- Operation ID: `get_alerts`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--user-id` | The ID of the user to get alerts for Location: query. Type: string. Optional. |
+| `--page` | The page number to get Location: query. Type: integer. Optional. Default: `1`. |
+| `--per-page` | The number of items per page Location: query. Type: integer. Optional. Default: `10`. |
+| `--all` | Whether to get all the alerts Location: query. Type: boolean. Optional. Default: `false`. |
+| `--include-deleted` | Whether to include soft-deleted alerts Location: query. Type: boolean. Optional. Default: `false`. |
+
+### `asknews api alerts get-all-alert-logs`
+
+Get all alert logs.
+
+- Request: `GET /v1/chat/alerts/logs`
+- Operation ID: `get_all_alert_logs`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--alert-id` | The alert ID Location: query. Type: string. Optional. |
+| `--user-id` | The ID of the user to get logs for Location: query. Type: string. Optional. |
+| `--page` | The page number to get Location: query. Type: integer. Optional. Default: `1`. |
+| `--per-page` | The number of items per page Location: query. Type: integer. Optional. Default: `10`. |
+| `--all` | Whether to get all the alert logs Location: query. Type: boolean. Optional. Default: `false`. |
+| `--start-timestamp` | Timestamp to start search from Location: query. Type: string. Optional. |
+| `--end-timestamp` | Timestamp to end search at Location: query. Type: string. Optional. |
+
+### `asknews api alerts put-alert`
+
+Update an alert.
+
+- Request: `PUT /v1/chat/alerts/{alert_id}`
+- Operation ID: `put_alert`
+- Safety: `mutating`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--alert-id` | The alert ID Location: path. Type: string. Required. Format: uuid. |
+
+**Request body fields:**
+
+| Option | Type | Required | Description |
+| --- | --- | --- | --- |
+| `--query` | string or null | no | The query to run for retrieving information from sources, and for checking the alert. If you have defined one or more reports, specify each report's individual query in the report prompt. |
+| `--sources` | array or null | no | The sources to use for retrieving information related to the alert query. Available sources are: AskNewsSource, TelegramSource, BlueskySource, WebSource, DeepNewsSource |
+| `--alert-type` | string or null | no | The type of alert. If specified, overrides `repeat` and `always_trigger`. 'AlwaysAlertWhen': trigger alert actions any time the alert query is satisfied (`repeat=True`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'AlertOnceIf': trigger alert actions when the alert query is satisfied and then disable the alert (`repeat=False`, `always_trigger=False`). Add Report model if you want a report when this is triggered. 'ReportAbout': always trigger alert actions according to cron schedule and write a report (`repeat=True`, `always_trigger=True`). Defaults to using DeepNews for the report unless specified. |
+| `--model` | string or null | no | The model that is used to check if the alert conditions are satisfied by sources (this is not the same as the model used to write the report.) |
+| `--cron` | string or null | no | How often or when to check sources for this alert, specified as a cron expression. Examples: '0 * * * *' (hourly), '0 9 * * *' (daily at 9am), '0 9 * * 1' (Mondays at 9am). See https://crontab.run/ for more examples. |
+| `--triggers` | array or null | no | Configuration for actions to trigger for the alert. Available actions are: WebhookAction, EmailAction, ResendBroadcastAction, GoogleDocsAction |
+| `--always-trigger` | boolean or null | no | Whether to always trigger the actions when sources are scanned. This skips the check for if the alert conditions are satisfied and run triggers immediately. Defaults to False. |
+| `--repeat` | boolean or null | no | Whether to repeat the alert. Default is True. If False, the alert will be disabled after it triggers once. |
+| `--active` | boolean or null | no | Whether the alert is active or not. Default is True. |
+| `--expires-at` | string or null | no | The expiration date for the alert. Default is None. If set, the alert will be disabled after this date. |
+| `--report` | object or array or null | no | Configuration for generating a written report when the alert triggers. If report is a list, the individual reports will be concatenated into one report in the order they are defined. If not specified, no report is generated. Use ReportRequest(identifier='deepnews', ...) for DeepNews reports.Use ReportRequest(...) or ReportRequest(identifier='legacy', ...) for legacy reports (DEPRECATED). Requests without identifier default to 'deepnews'. Only DeepNews reports can be used in list. |
+| `--title` | string or null | no | The title of the alert. If not provided, no title will be used. |
+| `--share-link` | string or null | no | The newsplunker share link to update when the alert triggers. |
+
+Use direct kebab-case body options, `--body '{...}'`, or `--body @request.json`.
+Direct body options override values supplied through `--body`.
+
+This operation requires confirmation and `--yes` in non-interactive use.
+
+### `asknews api alerts run-alert`
+
+Get an alert.
+
+- Request: `GET /v1/chat/alerts/{alert_id}/run`
+- Operation ID: `run_alert`
+- Safety: `mutating`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--alert-id` | The alert ID Location: path. Type: string. Required. Format: uuid. |
+| `--user-id` | The ID of the user to get logs for Location: query. Type: string. Optional. |
+| `--is-test` | Whether this is a test run Location: query. Type: boolean. Optional. Default: `false`. |
+
+This operation requires confirmation and `--yes` in non-interactive use.
+
+## Global options
+
+All commands support `--output human|table|json|jsonl|yaml`, `--json`, API/auth URL
+overrides, request timeout, and color control. Result data is written to stdout; diagnostics
+are written to stderr.

package/skills/asknews-cli/references/commands/api-analytics.md

@@ -0,0 +1,31 @@
+# api analytics
+
+Generated from AskNews API 0.24.95.
+
+## Operations
+
+### `asknews api analytics get-asset-sentiment`
+
+Get the news sentiment for a given asset during a provided period of time.
+
+This endpoint is good for narrow AI, like using in combination with a regressor
+to forecast prices etc.
+
+- Request: `GET /v1/analytics/finance/sentiment`
+- Operation ID: `get_asset_sentiment`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--asset` | The asset name to query for sentiment. Location: query. Type: string. Required. Choices: bitcoin, ethereum, cardano, uniswap, ripple, solana, polkadot, polygon, chainlink, tether, dogecoin, monero, tron, binance, aave, tesla, microsoft, amazon. |
+| `--metric` | The metric to obtain. Weighted metrics account for page-rank of original source. Higher page rank sources are weighted more heavily. Location: query. Type: string. Optional. Choices: news_positive, news_negative, news_total, news_positive_weighted, news_negative_weighted, news_total_weighted. Default: `"news_positive"`. |
+| `--date-from` | The start date in ISO format Location: query. Type: string. Optional. |
+| `--date-to` | The end date in ISO format Location: query. Type: string. Optional. |
+
+## Global options
+
+All commands support `--output human|table|json|jsonl|yaml`, `--json`, API/auth URL
+overrides, request timeout, and color control. Result data is written to stdout; diagnostics
+are written to stderr.

package/skills/asknews-cli/references/commands/api-autofilter.md

@@ -0,0 +1,31 @@
+# api autofilter
+
+Generated from AskNews API 0.24.95.
+
+## Operations
+
+### `asknews api autofilter autofilter`
+
+This is a helper endpoint designed to intelligently populate the
+"parameters of the /news search endpoint of AskNews. It takes a description
+of the type of news that you want to access, and then maps it to the available
+parameters automatically.
+
+This endpoint returns the parameters, called filter_params, which can be used
+in a variety of other AskNews endpoints, for example, /news, /graph, /chat.
+
+- Request: `GET /v1/chat/autofilter`
+- Operation ID: `autofilter`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--query` | A description of what kind of news you want to get. Location: query. Type: string. Required. |
+
+## Global options
+
+All commands support `--output human|table|json|jsonl|yaml`, `--json`, API/auth URL
+overrides, request timeout, and color control. Result data is written to stdout; diagnostics
+are written to stderr.

package/skills/asknews-cli/references/commands/api-byok.md

@@ -0,0 +1,72 @@
+# api byok
+
+Generated from AskNews API 0.24.95.
+
+## Operations
+
+### `asknews api byok delete-byok-key`
+
+Delete a stored BYOK API key for a provider.
+Bring your own key is reserved for enterprise clients.
+If you want to use this feature, please contact us at contact@asknews.app
+
+- Request: `DELETE /v1/byok/{provider}`
+- Operation ID: `delete_byok_key`
+- Safety: `mutating`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--provider` | The BYOK provider Location: path. Type: string. Required. Choices: anthropic, google. |
+
+This operation requires confirmation and `--yes` in non-interactive use.
+
+### `asknews api byok get-byok-key`
+
+Get the stored BYOK API key hint for a provider.
+Bring your own key is reserved for enterprise clients.
+If you want to use this feature, please contact us at contact@asknews.app
+
+- Request: `GET /v1/byok/{provider}`
+- Operation ID: `get_byok_key`
+- Safety: `read-only`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--provider` | The BYOK provider Location: path. Type: string. Required. Choices: anthropic, google. |
+
+### `asknews api byok upsert-byok-key`
+
+Store a BYOK API key for a provider.
+Bring your own key is reserved for enterprise clients.
+If you want to use this feature, please contact us at contact@asknews.app
+
+- Request: `PUT /v1/byok/{provider}`
+- Operation ID: `upsert_byok_key`
+- Safety: `mutating`
+
+**Options:**
+
+| Option | Description |
+| --- | --- |
+| `--provider` | The BYOK provider Location: path. Type: string. Required. Choices: anthropic, google. |
+
+**Request body fields:**
+
+| Option | Type | Required | Description |
+| --- | --- | --- | --- |
+| `--api-key` | string | yes |  |
+
+Use direct kebab-case body options, `--body '{...}'`, or `--body @request.json`.
+Direct body options override values supplied through `--body`.
+
+This operation requires confirmation and `--yes` in non-interactive use.
+
+## Global options
+
+All commands support `--output human|table|json|jsonl|yaml`, `--json`, API/auth URL
+overrides, request timeout, and color control. Result data is written to stdout; diagnostics
+are written to stderr.