@vk007/autocli 0.1.0

package/package.json

@@ -0,0 +1,83 @@
+{
+  "name": "@vk007/autocli",
+  "version": "0.1.0",
+  "description": "Terminal automation toolkit for developers and AI agents across LLMs, social platforms, developer tools, editors, data tools, and public utilities.",
+  "type": "module",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/vkop007/autocli.git"
+  },
+  "homepage": "https://github.com/vkop007/autocli#readme",
+  "bugs": {
+    "url": "https://github.com/vkop007/autocli/issues"
+  },
+  "packageManager": "bun@1.3.6",
+  "keywords": [
+    "bun",
+    "cli",
+    "automation",
+    "instagram",
+    "twitter",
+    "x"
+  ],
+  "bin": {
+    "autocli": "./dist/index.js"
+  },
+  "files": [
+    "dist",
+    "README.md",
+    "skills"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "engines": {
+    "bun": ">=1.3.0",
+    "node": ">=20.11.0"
+  },
+  "scripts": {
+    "dev": "bun run src/index.ts",
+    "dev:watch": "bun run --watch src/index.ts",
+    "start": "bun run src/index.ts",
+    "prepare": "bun run build",
+    "prepublishOnly": "bun run typecheck && bun test && bun run build",
+    "link:global": "bun run scripts/link-global.ts",
+    "typecheck": "tsc --noEmit",
+    "build": "bun build --target=node --format=esm --external tlsclientwrapper --external playwright-core --outdir dist ./src/index.ts",
+    "build:bin": "bun build --compile --target=bun --external playwright-core --outfile bin/autocli ./src/index.ts",
+    "test": "bun test"
+  },
+  "dependencies": {
+    "@whiskeysockets/baileys": "^7.0.0-rc.9",
+    "commander": "^14.0.3",
+    "csv-parse": "^6.2.1",
+    "csv-stringify": "^6.7.0",
+    "fast-xml-parser": "^5.5.9",
+    "fetch-cookie": "^3.2.0",
+    "marked": "^17.0.5",
+    "open-location-code": "^1.0.3",
+    "ora": "^9.3.0",
+    "pdf-lib": "^1.17.1",
+    "picocolors": "^1.1.1",
+    "playwright-core": "^1.58.2",
+    "qrcode-terminal": "^0.12.0",
+    "telegram": "^2.26.22",
+    "tlsclientwrapper": "^4.2.0",
+    "tough-cookie": "^6.0.1",
+    "turndown": "^7.2.2",
+    "ws": "^8.20.0",
+    "yaml": "^2.8.3",
+    "zod": "^4.3.6"
+  },
+  "devDependencies": {
+    "@types/node": "^24.10.1",
+    "@types/turndown": "^5.0.6",
+    "@types/ws": "^8.18.1",
+    "bun-types": "^1.3.11",
+    "typescript": "^5.9.3"
+  },
+  "trustedDependencies": [
+    "koffi"
+  ]
+}

package/skills/autocli/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: autocli
+description: Use when a task can be completed through the AutoCLI command line instead of custom scripts. Helps agents choose the right category and provider, prefer --json output, use shared browser login or saved sessions safely, inspect health with status/doctor/sessions, and use session-aware tools like tools http before inventing custom web automation.
+---
+
+# AutoCLI
+
+Use this skill when the task maps to an existing AutoCLI provider or when you need to operate the AutoCLI repository itself.
+
+## Quick Rules
+
+- Always use category-based commands: `autocli <category> <provider> ...`
+- Prefer `--json` for agent work unless the user explicitly wants human-readable output.
+- If auth state is unclear, start with `autocli status --json` or `autocli doctor --json`.
+- Check saved sessions with `autocli sessions --json` before asking for a fresh cookie export or token.
+- Use `autocli <category> <provider> capabilities --json` when you need to confirm auth type, stability, browser support, or read/write boundaries before planning a task.
+- Prefer providers whose `capabilities --json` report `stability: stable` when you have multiple valid options.
+- For cookie-backed providers, prefer `autocli login --browser` and then `<provider> login --browser` when manual cookie export would be awkward.
+- Use `autocli tools http <provider-or-domain> inspect|request|capture` when a saved web session exists but the exact provider command is missing or unclear.
+- For risky actions, read or list first, then mutate second.
+- Use `autocli <category> --help` and `autocli <category> <provider> --help` before assuming subcommands.
+- Some web-session providers are partial. If a route feels limited, consult the repo `README.md` support notes and the provider help text.
+
+## Core Workflow
+
+1. Map the task to a category. If unsure, read [references/category-map.md](references/category-map.md).
+2. Confirm whether the provider is public, cookie-backed, session-backed, API-token-based, bot-token-based, or local-tool-based.
+3. If the provider is unfamiliar or risky, run `capabilities --json` before acting.
+4. If the provider needs auth and no saved session exists, run `login` first.
+5. For cookie-backed providers, choose the cleanest auth path:
+   - `login --browser` when the user can sign in interactively
+   - `login --cookies ...` when they already have an export
+6. Prefer discovery commands like `search`, `me`, `profile`, `status`, `page`, `title`, `posts`, `spaces`, `projects`, `services`, or `apps` before write commands.
+7. When you need to pass results to another command, use `--json` and route through `autocli data ...` if transformation is needed.
+8. If the provider is authenticated but the exact action is not modeled yet, try `autocli tools http ...` before reaching for custom curl or browser automation.
+
+## Result Conventions
+
+- Many list-style commands expose a stable `data.items` alias even if the native provider key is `repos`, `projects`, `posts`, or something else.
+- Many singular reads expose a stable `data.entity` alias even if the native provider key is `profile`, `page`, `movie`, or `project`.
+- `data.meta.count` and `data.meta.listKey` give a quick summary for list results.
+- `data.guidance.recommendedNextCommand` and `data.guidance.nextCommands` are safe follow-up hints the agent should prefer over guessing.
+
+## Global Commands
+
+- `autocli login --browser`
+- `autocli status --json`
+- `autocli doctor --json`
+- `autocli sessions --json`
+- `autocli sessions show <platform> <account> --json`
+- `autocli <category> <provider> capabilities --json`
+
+## High-Value Patterns
+
+- Use `login --browser` once to bootstrap the shared AutoCLI browser profile, then reuse it for later cookie-backed logins.
+- Use `capabilities --json` to let the agent verify support level before it attempts mutations or browser fallbacks.
+- Treat provider help as machine guidance too: `--help` now includes a generated `Quick Start`, `Support Profile`, and `Stability Guide`.
+- Use `tools` and `data` as glue around other providers.
+- Use `tools http` to inspect saved web sessions, replay authenticated requests, and capture logged-in traffic from the shared browser.
+- Use `editor` for local transformations before upload or posting.
+- Use `news`, `movie`, `music`, `maps`, `finance`, and many `tools` providers for public lookup tasks with no login step.
+- Use `developer`, `social`, `llm`, `shopping`, `devops`, and some `music` providers when the task needs an account-backed action.
+
+## Common Examples
+
+```bash
+autocli login --browser
+autocli developer github capabilities --json
+autocli developer github login --browser
+autocli developer github me --json
+autocli social reddit search "bun cli" --json
+autocli devops render services --json
+autocli tools http github inspect --json
+autocli tools page-links https://example.com --type external --json
+autocli data json query '{"items":[{"title":"AutoCLI"}]}' 'items[0].title'
+autocli editor image resize ./photo.png --width 1200
+```
+
+## Failure Recovery
+
+- If a login-based provider fails unexpectedly, run `autocli sessions --json` and `autocli doctor --json`.
+- If a cookie-backed provider says the session expired, re-login with `login --browser` or re-import cookies with `login --cookies ...`.
+- If a site works in the shared browser but not through its modeled provider commands yet, use `autocli tools http <provider-or-domain> inspect` or `capture`.
+- If a command depends on local binaries, `doctor` will show missing tools such as `ffmpeg`, `qpdf`, `tesseract`, or other local dependencies.
+- If a provider exposes async media jobs, prefer its `status`, `wait`, `download`, or `cancel` subcommands instead of polling manually.
+
+## When To Read More
+
+- Read [references/category-map.md](references/category-map.md) when you need a quick category/provider chooser, auth hint, or example command pattern.

package/skills/autocli/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "AutoCLI"
+  short_description: "Use AutoCLI providers, browser login, and session-aware tools correctly"
+  default_prompt: "Use $autocli to choose the right AutoCLI category and provider, check provider capabilities before risky actions, prefer --json for agent work, use shared browser login or saved sessions safely, and fall back to tools http when a logged-in web action is not fully modeled yet."
+
+policy:
+  allow_implicit_invocation: true

package/skills/autocli/references/category-map.md

@@ -0,0 +1,53 @@
+# AutoCLI Category Map
+
+Use this file when you need to choose the right AutoCLI surface quickly.
+
+## Global Commands
+
+- `login --browser`: open AutoCLI's shared browser profile for interactive sign-in
+- `status`: summary of CLI and connection health
+- `doctor`: environment checks, saved sessions, and missing binaries
+- `sessions`: inspect or remove saved connections
+- `<category> <provider> capabilities`: machine-readable provider support metadata
+
+## Categories
+
+| Category | Use it for | Representative providers | Typical commands |
+| --- | --- | --- | --- |
+| `llm` | prompting and generation | `chatgpt`, `gemini`, `grok`, `mistral`, `perplexity`, `qwen` | `login`, `status`, `text`, `image`, `video` |
+| `social` | posting, profile lookup, messaging, public social reads | `x`, `instagram`, `reddit`, `bluesky`, `mastodon`, `telegram`, `whatsapp`, `youtube` | `login`, `me`, `profile`, `posts`, `thread`, `post`, `comment`, `send` |
+| `developer` | code hosting, docs, issues, workspace tools | `github`, `gitlab`, `jira`, `linear`, `trello`, `confluence`, `notion` | `login`, `me`, `projects`, `issues`, `page`, `search` |
+| `devops` | infrastructure, deploys, DNS, and platform operations | `cloudflare`, `vercel`, `supabase`, `render`, `railway`, `netlify`, `digitalocean`, `fly` | `login`, `me`, `zones`, `projects`, `services`, `apps`, `deployments` |
+| `editor` | local file and media editing | `image`, `video`, `audio`, `pdf`, `document`, `subtitle`, `gif`, `archive` | `info`, `convert`, `resize`, `split`, `watermark`, `ocr` |
+| `data` | structured data cleanup and transformation | `json`, `csv`, `yaml`, `xml`, `html`, `markdown`, `text` | `format`, `query`, `to-json`, `filter`, `text`, `replace` |
+| `tools` | public utilities, session-aware HTTP inspection, and web helpers | `http`, `websearch`, `translate`, `page-links`, `favicon`, `headers`, `rss`, `timezone` | `inspect`, `capture`, `request`, and other lookup-style commands |
+| `news` | public headline and feed discovery | `news` | `top`, `search`, `sources`, `feed` |
+| `maps` | geocoding, routing, geometry | `openstreetmap`, `osrm`, `geo` | `search`, `reverse`, `route`, `distance`, `elevation` |
+| `finance` | market and forex lookups | `stocks`, `crypto`, `currency` | quote and conversion commands |
+| `movie` | title lookup, recommendations, streaming availability | `tmdb`, `imdb`, `letterboxd`, `justwatch`, `anilist` | `search`, `title`, `recommendations`, `trending` |
+| `music` | music discovery and playback surfaces | `soundcloud`, `bandcamp`, `deezer`, `spotify`, `youtube-music` | `search`, `track`, `album`, `playlist`, playback controls |
+| `shopping` | product discovery and account shopping actions | `amazon`, `ebay`, `etsy`, `flipkart` | `search`, `product`, `cart`, `orders` |
+| `bot` | bot-token messaging and chat ops | `telegrambot`, `discordbot`, `slackbot`, `githubbot` | `login`, `send`, `channels`, `issues` |
+
+## Auth Expectations
+
+| Needs | Meaning |
+| --- | --- |
+| `none` | Public or local functionality |
+| `cookies` | Use `login --cookies ...` or `login --browser` for a saved web session |
+| `cookies + local token` | Cookie-backed session plus a token stored in site storage |
+| `session` | Do one interactive login once, then reuse the saved user session |
+| `api token` | Save a personal or service token once with `login --token ...` |
+| `bot token` | Save a bot token once with `login --token ...` |
+| `local tools` | Requires binaries like `ffmpeg`, `qpdf`, or `tesseract` |
+
+## Safe Agent Defaults
+
+- Use `--json` unless the user clearly wants formatted terminal output.
+- Prefer read-only commands before mutations.
+- Use `capabilities --json` before risky or unfamiliar provider actions so the agent can see auth type, stability, browser support, and read/write boundaries.
+- Use `doctor` and `sessions` before assuming auth is broken.
+- If the user can sign in interactively, prefer `autocli login --browser` and then the provider's `login --browser`.
+- If a provider is authenticated but missing a modeled action, try `autocli tools http <provider-or-domain> inspect` before inventing custom automation.
+- For nested help, use `autocli <category> --help` then `autocli <category> <provider> --help`.
+- Do not use flat legacy forms like `autocli github ...` or `autocli chatgpt ...`.