niahere 0.2.11 → 0.2.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "niahere",
-  "version": "0.2.11",
+  "version": "0.2.13",
   "description": "A personal AI assistant daemon — scheduled jobs, chat across Telegram and Slack, persona system, and visual identity.",
   "type": "module",
   "scripts": {

package/skills/modal-cli/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: modal-cli
+description: >
+  Modal CLI for serverless GPU/cloud compute. Use when user mentions modal, deploying to modal,
+  running GPU workloads, or serverless Python functions.
+  Check `which modal` first — if missing, offer: `pip install modal && modal setup`.
+  Covers run/serve/deploy, apps, containers, secrets, volumes, and workspace management.
+---
+
+## Prerequisites
+
+Before any modal command, verify the CLI is available:
+
+```bash
+which modal
+```
+
+**If not found**, ask the user:
+
+> Modal CLI not found. Install it?
+>
+> ```bash
+> pip install modal
+> ```
+
+After install, run auth setup:
+
+```bash
+modal setup
+```
+
+This opens a browser for token auth. If `modal` still isn't on PATH after pip install, use:
+
+```bash
+python -m modal setup
+```
+
+**If found but not authed**, check with:
+
+```bash
+modal token info
+```
+
+If that errors, run `modal setup` to authenticate.
+
+## Core Commands
+
+| Command | Purpose |
+|---------|---------|
+| `modal run <file>` | One-off execution of a script/function |
+| `modal serve <file>` | Local dev with hot-reload |
+| `modal deploy <file>` | Production deployment |
+| `modal app list` | List deployed apps |
+| `modal app logs <name>` | Stream logs for a deployed app |
+| `modal app stop <name>` | Stop a running app |
+| `modal shell` | Interactive shell in Modal environment |
+
+## Workflows
+
+### First-time setup
+```bash
+pip install modal
+modal setup
+modal run hello.py  # validate end-to-end
+```
+
+### Develop and deploy
+```bash
+modal run my_app.py        # test locally
+modal serve my_app.py      # hot-reload dev
+modal deploy my_app.py     # ship it
+```
+
+### Debug containers
+```bash
+modal container list
+modal container logs <id>
+modal container exec <id> -- bash -lc "nvidia-smi"
+```
+
+### Manage resources
+```bash
+modal secret create my-secret KEY=value
+modal volume create my-vol
+modal environment create dev
+modal config set-environment dev
+```
+
+## Auth & Profiles
+
+- `modal token info` — check current auth
+- `modal token new` — create token via browser
+- `modal token set` — set token credentials directly
+- `modal profile list` / `activate` — switch workspaces
+- `modal config show` — print effective config
+
+Environment variables: `MODAL_TOKEN_ID`, `MODAL_TOKEN_SECRET`, `MODAL_ENVIRONMENT`, `MODAL_PROFILE`
+
+## Resource Management
+
+- **Secrets**: `modal secret list/create/delete` (supports `.env` import)
+- **Volumes**: `modal volume create/list/ls/put/get/rm/delete`
+- **Dicts**: `modal dict create/list/items/get/clear/delete`
+- **Queues**: `modal queue create/list/peek/len/clear/delete`
+- **NFS**: `modal nfs list/create/ls/put/get/rm/delete`
+- **Environments**: `modal environment list/create/delete/update`
+
+## Decision Points
+
+- User says "deploy to modal" / "run on GPU" → `modal deploy` or `modal run`
+- User says "check my modal apps" → `modal app list`
+- User says "modal logs" → `modal app logs <name>`
+- User needs interactive debug → `modal shell` or `modal container exec`
+- modal not installed → offer install, don't silently fail
+- modal not authed → run `modal setup`
+
+## References
+
+- Guide: https://modal.com/docs/guide
+- CLI reference: https://modal.com/docs/reference/cli/
+- Status: https://status.modal.com

package/skills/render-cli/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: render-cli
+description: >
+  Render CLI for deploying and managing services, databases, and blueprints on Render.
+  Use when user mentions render, deploying to render, render services, or render databases.
+  Check `which render` first — if missing, offer: `brew install render` (macOS) or curl installer.
+  Covers deploys, services, SSH, psql, blueprints, and CI workflows.
+---
+
+## Prerequisites
+
+Before any render command, verify the CLI is available:
+
+```bash
+which render
+```
+
+**If not found**, ask the user:
+
+> Render CLI not found. Install it?
+>
+> macOS:
+> ```bash
+> brew install render
+> ```
+>
+> Linux/macOS (alternative):
+> ```bash
+> curl -fsSL https://raw.githubusercontent.com/render-oss/cli/refs/heads/main/bin/install.sh | sh
+> ```
+
+After install, authenticate:
+
+```bash
+render login
+```
+
+Then set the active workspace:
+
+```bash
+render workspace set
+```
+
+**If found but not authed**, `render services` will fail — run `render login`.
+
+## Core Commands
+
+| Command | Purpose |
+|---------|---------|
+| `render services` | List services and datastores |
+| `render deploys create <id>` | Trigger a deploy |
+| `render deploys list <id>` | Deploy history |
+| `render ssh <id>` | SSH into a service |
+| `render psql <id>` | Postgres session |
+| `render blueprints validate` | Validate render.yaml |
+| `render workspaces` | List workspaces |
+
+## Workflows
+
+### First-time setup
+```bash
+brew install render   # or curl installer
+render login
+render workspace set
+render services       # verify access
+```
+
+### Deploy a service
+```bash
+render services                          # pick service
+render deploys create <SERVICE_ID>       # trigger deploy
+render deploys create <ID> --wait        # block until done
+render deploys create <ID> --commit <SHA>  # specific commit
+render deploys create <ID> --image <URL>   # docker image
+```
+
+### Database access
+```bash
+render psql <DATABASE_ID>                    # interactive session
+render psql <DATABASE_ID> -c "SELECT 1"      # one-shot query
+render psql <DATABASE_ID> -o json            # JSON output
+```
+
+### Debug a service
+```bash
+render ssh <SERVICE_ID>                  # interactive shell
+render ssh <SERVICE_ID> --ephemeral      # throwaway shell
+```
+
+### Validate blueprints
+```bash
+render blueprints validate               # defaults to ./render.yaml
+render blueprints validate my-render.yaml
+```
+
+## CI / Non-Interactive Mode
+
+Use `RENDER_API_KEY` (not login tokens) for automation:
+
+```bash
+RENDER_API_KEY=$RENDER_API_KEY render deploys create "$SERVICE_ID" --output json --confirm
+```
+
+- `--confirm` skips prompts
+- `--output` / `-o`: `json`, `yaml`, `text`, `interactive`
+- `RENDER_OUTPUT` env var sets default output format
+
+## Config
+
+- Config path: `~/.render/cli.yaml`
+- Override: `RENDER_CLI_CONFIG_PATH` env var
+- Re-auth: `render login` if token expires
+
+## Decision Points
+
+- User says "deploy to render" → `render deploys create`
+- User says "check render services" → `render services`
+- User needs DB access → `render psql`
+- User needs shell access → `render ssh`
+- User has render.yaml → `render blueprints validate`
+- render not installed → offer install, don't silently fail
+- render not authed → run `render login`
+
+## References
+
+- Docs: https://render.com/docs/cli
+- Releases: https://github.com/render-oss/cli/releases
+- Source: https://github.com/render-oss/cli