superacli 1.13.0 → 1.14.0

package/plugins/mime-cli/skills/quickstart/SKILL.md

@@ -1,49 +0,0 @@
----
-name: mime-cli
-description: Use this skill when the user wants to detect MIME types of files.
----
-
-# Mime-CLI Plugin
-
-Detect MIME types of files.
-
-## Commands
-
-### MIME Detection
-- `mime-cli file type` — Detect MIME type of file
-
-## Usage Examples
-- "mime-cli file type --file image.png"
-- "mime-cli file type --file document.pdf"
-
-## Installation
-
-```bash
-npm install -g mime-cli
-```
-
-## Examples
-
-```bash
-# Detect MIME type
-mime file.txt
-
-# Check multiple files
-mime file1.txt file2.jpg file3.pdf
-
-# Use glob pattern
-mime *.png
-
-# Check extension only
-mime --ext .json
-
-# Reverse lookup (MIME to extension)
-mime --reverse application/json
-```
-
-## Key Features
-- MIME type detection
-- Extension to MIME mapping
-- MIME to extension lookup
-- Batch file checking
-- Glob pattern support

package/plugins/mime-type/skills/quickstart/SKILL.md

@@ -1,9 +0,0 @@
----
-name: mime-type
-description: Detect MIME type from filename.
----
-# mime-type Plugin
-Get the MIME type for any file extension.
-## Usage
-- `mime detect type image.png` → image/png
-- `mime detect type document.pdf` → application/pdf

package/plugins/mimeo/skills/quickstart/SKILL.md

@@ -1,25 +0,0 @@
----
-name: mimeo
-description: Use this skill when the user wants to convert expert knowledge or domain expertise into reusable SKILL.md or AGENTS.md files for AI agents.
----
-
-# Mimeo — Expert to SKILL.md Converter
-
-Mimeograph an expert into a SKILL.md or AGENTS.md. Convert structured or unstructured expertise into reusable, composable skill files for AI agents.
-
-## Installation
-```bash
-git clone https://github.com/K-Dense-AI/mimeo.git
-sc skills teach mimeo:quickstart
-```
-
-## What It Does
-- Takes expert knowledge (interviews, docs, conversations)
-- Produces structured SKILL.md or AGENTS.md files
-- Compatible with Claude Code, Codex, Cursor, and all SKILL.md runtimes
-- Makes domain expertise reusable by AI agents
-
-## Usage Prompts
-- "Convert this documentation into a SKILL.md for my AI agent"
-- "Create an AGENTS.md file capturing our deployment best practices"
-- "Mimeograph my expertise on Kubernetes networking into a skill file"

package/plugins/miniconda/skills/quickstart/SKILL.md

@@ -1 +0,0 @@
----\nname: miniconda\ndescription: Minimal Conda installer\n---\n# miniconda Plugin\nMinimal Conda installer

package/plugins/minikube/skills/quickstart/SKILL.md

@@ -1,17 +0,0 @@
----
-name: minikube
-description: Use this skill when the user wants to use the minikube command-line tool.
----
-
-# minikube Plugin
-
-Local Kubernetes cluster for development
-
-## Commands
-- `minikube self version` — Print version
-- `minikube _ _` — Passthrough to minikube
-
-## Installation
-```bash
-brew install minikube
-```

package/plugins/minio/skills/quickstart/SKILL.md

@@ -1,36 +0,0 @@
----
-name: minio
-description: Use this skill when the user wants to high performance object storage with s3 compatible api.
----
-
-# Minio Plugin
-
-High performance object storage with S3 compatible API.
-
-## Commands
-
-### Operations
-- `minio bucket ls` — ls bucket via mc
-- `minio bucket mb` — mb bucket via mc
-- `minio object cp` — cp object via mc
-- `minio object mirror` — mirror object via mc
-
-## Usage Examples
-- "minio --help"
-- "minio <args>"
-
-## Installation
-
-```bash
-brew install minio/stable/mc
-```
-
-## Examples
-
-```bash
-mc --version
-mc --help
-```
-
-## Key Features
-- s3\n- object-storage\n- cloud

package/plugins/minipostiz-cli/skills/bluesky-setup/SKILL.md

@@ -1,86 +0,0 @@
----
-name: minipostiz-bluesky-setup
-description: Bluesky AT Protocol setup for minipostiz-cli — create app password, store handle + password
-type: setup
----
-
-# minipostiz-cli — Bluesky Setup
-
-Bluesky uses the AT Protocol. Authentication is a handle + app password (never your main account password).
-
-## What you need
-
-| Credential | Flag |
-|------------|------|
-| Handle | `--handle` (e.g. `yourname.bsky.social`) |
-| App Password | `--password` |
-
----
-
-## Step 1 — Create an App Password
-
-1. Go to https://bsky.app → **Settings** (bottom-left)
-2. **Privacy and Security** → **App Passwords**
-3. Click **Add App Password**
-4. Give it a name (e.g. `minipostiz`) → **Create App Password**
-5. Copy the generated password — format: `xxxx-xxxx-xxxx-xxxx`
-
-> **Never use your main account password.** App passwords are scoped and revocable.
-
----
-
-## Step 2 — Find your handle
-
-Your handle is visible on your profile: `@yourname.bsky.social`
-Custom domains (e.g. `yourname.com`) also work as handles.
-
----
-
-## Step 3 — Store in minipostiz-cli
-
-```bash
-minipostiz auth --platform bluesky \
-  --handle "yourname.bsky.social" \
-  --password "xxxx-xxxx-xxxx-xxxx"
-
-# Or via supercli
-sc minipostiz auth set-bluesky \
-  --handle "yourname.bsky.social" \
-  --password "xxxx-xxxx-xxxx-xxxx"
-```
-
----
-
-## Step 4 — Test
-
-```bash
-minipostiz auth verify --platform bluesky
-minipostiz publish --platform bluesky --message "Hello from minipostiz-cli"
-```
-
----
-
-## Custom / self-hosted instance
-
-If you run your own PDS (Personal Data Server):
-
-```bash
-minipostiz auth --platform bluesky \
-  --handle "yourname.example.com" \
-  --password "xxxx-xxxx-xxxx-xxxx" \
-  --host "https://your-pds.example.com"
-```
-
----
-
-## Troubleshooting
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `Authentication Required` | Wrong handle or password | Double-check handle format (no `@`); use app password not main password |
-| `Invalid identifier` | Handle format wrong | Use full handle: `name.bsky.social` not just `name` |
-| `Token has been revoked` | App password deleted | Create a new app password at bsky.app → Settings |
-
-## Token lifetime
-
-App passwords **do not expire** but can be revoked at any time from Settings → App Passwords.

package/plugins/minipostiz-cli/skills/devto-setup/SKILL.md

@@ -1,96 +0,0 @@
----
-name: minipostiz-devto-setup
-description: Dev.to API setup for minipostiz-cli — generate API key, store credentials, posting format
-type: setup
----
-
-# minipostiz-cli — Dev.to Setup
-
-Dev.to has a simple REST API. One API key is all you need.
-
-## What you need
-
-| Credential | Flag |
-|------------|------|
-| API Key | `--apiKey` |
-| Tags (optional) | `--tags` (comma-separated, max 4) |
-| Series (optional) | `--series` |
-
----
-
-## Step 1 — Generate an API Key
-
-1. Go to https://dev.to → sign in
-2. Click your avatar → **Settings**
-3. **Extensions** → **DEV Community API Keys**
-4. Enter a description (e.g. `minipostiz`) → **Generate API Key**
-5. Copy the key — it's shown once (but you can generate multiple)
-
----
-
-## Step 2 — Store in minipostiz-cli
-
-```bash
-minipostiz auth --platform devto --apiKey "YOUR_API_KEY"
-
-# With optional defaults
-minipostiz auth --platform devto \
-  --apiKey "YOUR_API_KEY" \
-  --tags "webdev,productivity,tools" \
-  --series "My Series Name"
-
-# Or via supercli
-sc minipostiz auth set-devto --apiKey "YOUR_API_KEY"
-```
-
----
-
-## Step 3 — Test
-
-```bash
-minipostiz auth verify --platform devto
-minipostiz publish --platform devto --message "# My First Post
-
-This is the body of the article published via minipostiz-cli."
-```
-
----
-
-## Post format
-
-Dev.to posts are **articles**. minipostiz-cli maps:
-- **First line** of `--message` → article title (markdown heading stripped)
-- **Remaining lines** → article body (markdown supported)
-
-```bash
-minipostiz publish --platform devto --message "# Article Title
-
-## Introduction
-
-Body content here. Supports **bold**, *italic*, \`code\`, etc."
-```
-
----
-
-## Optional: tags and series
-
-Tags and series can be set at auth time (applied to all posts) or overridden:
-
-```bash
-# Update auth to set default tags
-minipostiz auth --platform devto --apiKey "KEY" --tags "javascript,node,cli"
-```
-
----
-
-## Troubleshooting
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `401 Unauthorized` | Invalid API key | Regenerate key at dev.to → Settings → Extensions |
-| `422 Unprocessable` | Article validation failed | Ensure title (first line) is non-empty |
-| Post published but no tags | Tags not in auth | Add `--tags` to `minipostiz auth --platform devto` |
-
-## Token lifetime
-
-Dev.to API keys **do not expire** unless deleted from Settings → Extensions.

package/plugins/minipostiz-cli/skills/discord-setup/SKILL.md

@@ -1,71 +0,0 @@
----
-name: minipostiz-discord-setup
-description: Discord webhook setup for minipostiz-cli — create webhook in a channel, store URL
-type: setup
----
-
-# minipostiz-cli — Discord Setup
-
-Discord uses webhooks for posting — no OAuth app or bot required. One URL is all you need.
-
-## What you need
-
-| Credential | Flag |
-|------------|------|
-| Webhook URL | `--webhookUrl` |
-
----
-
-## Step 1 — Create a Webhook
-
-**In Discord desktop or browser:**
-
-1. Open your server → right-click the target channel → **Edit Channel**
-2. Go to **Integrations** → **Webhooks** → **New Webhook**
-3. Set a name (e.g. `minipostiz`) and optionally upload an avatar
-4. Click **Copy Webhook URL** → save it
-5. Click **Save**
-
-**Shortcut:** Channel Settings gear icon → Integrations → Webhooks
-
----
-
-## Step 2 — Store in minipostiz-cli
-
-```bash
-minipostiz auth --platform discord \
-  --webhookUrl "https://discord.com/api/webhooks/CHANNEL_ID/TOKEN"
-
-# Or via supercli
-sc minipostiz auth set-discord \
-  --webhookUrl "https://discord.com/api/webhooks/CHANNEL_ID/TOKEN"
-```
-
----
-
-## Step 3 — Test
-
-```bash
-minipostiz auth verify --platform discord
-minipostiz publish --platform discord --message "Hello from minipostiz-cli"
-```
-
----
-
-## Multiple channels
-
-To post to multiple Discord channels, use multiple webhook credentials under different platform aliases — or use comma-separated platforms with separate auth entries per server/channel.
-
----
-
-## Troubleshooting
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `404 Unknown Webhook` | Webhook was deleted | Create a new webhook |
-| `401 Invalid Webhook Token` | URL was regenerated | Copy the new URL from channel settings |
-| `400 Cannot send empty message` | Empty message string | Ensure `--message` is non-empty |
-
-## Token lifetime
-
-Webhook URLs **do not expire** but can be deleted or regenerated from Channel Settings → Integrations.

package/plugins/minipostiz-cli/skills/facebook-setup/SKILL.md

@@ -1,121 +0,0 @@
----
-name: minipostiz-facebook-setup
-description: Facebook Graph API setup for minipostiz-cli — create app, get page access token + page ID, store credentials
-type: setup
----
-
-# minipostiz-cli — Facebook Setup
-
-minipostiz-cli posts to **Facebook Pages** (not personal profiles — the Graph API doesn't support personal timeline posts). You need a Page Access Token and the Page ID.
-
-## What you need
-
-| Credential | Flag |
-|------------|------|
-| Page Access Token | `--pageAccessToken` |
-| Page ID | `--pageId` |
-
----
-
-## Step 1 — Create a Facebook App
-
-1. Go to https://developers.facebook.com/apps → **Create App**
-2. Choose **"Authenticate and request data from users"** use case (Consumer type) → **Next**
-   - ⚠️ Do NOT pick Business type — it won't show `pages_manage_posts` in Graph Explorer
-3. Fill in app name and contact email → **Create App**
-
----
-
-## Step 2 — Add Pages permissions via Use Cases
-
-The new Facebook developer dashboard (2024+) uses **use cases** instead of individual permission requests:
-
-1. In your app dashboard → click **"Customize the Manage everything on your Page use case"**
-2. Add the following permissions to that use case:
-   - `pages_manage_posts`
-   - `pages_read_engagement`
-3. Save — these are available in development mode without App Review for pages you admin
-
-> **Note:** There is no longer an "App Review → Permissions and Features" link in the dashboard. The use case customization screen is the replacement.
-
----
-
-## Step 3 — Get your Page Access Token
-
-**Via Graph API Explorer (recommended):**
-
-1. Go to https://developers.facebook.com/tools/explorer/
-2. Select your app in the **Application** dropdown
-3. Click the blue **Generate Access Token** button (opens a Facebook Login popup — NOT "Get App Token")
-4. In the **Permissions** list, add `pages_manage_posts` and `pages_read_engagement`
-5. Authorize → in the **User or Page** dropdown → switch to your **Page** (e.g. "Savoie Tech")
-6. Copy the Page Access Token shown
-
-**Get your Page ID and a proper Page Token via curl (alternative):**
-
-```bash
-# Use the User token to list all pages you manage + their page tokens
-curl "https://graph.facebook.com/v21.0/me/accounts?access_token=YOUR_USER_TOKEN"
-# Response includes each page's id and access_token — use those directly
-```
-
-**Get a long-lived token (60 days instead of ~1 hour):**
-
-```bash
-curl "https://graph.facebook.com/v21.0/oauth/access_token?\
-  grant_type=fb_exchange_token&\
-  client_id=YOUR_APP_ID&\
-  client_secret=YOUR_APP_SECRET&\
-  fb_exchange_token=YOUR_SHORT_LIVED_PAGE_TOKEN"
-```
-
----
-
-## Step 4 — Store in minipostiz-cli
-
-```bash
-minipostiz auth --platform facebook \
-  --pageAccessToken "YOUR_PAGE_ACCESS_TOKEN" \
-  --pageId "123456789012345"
-
-# Or via supercli
-sc minipostiz auth set-facebook \
-  --pageAccessToken "YOUR_PAGE_ACCESS_TOKEN" \
-  --pageId "123456789012345"
-```
-
----
-
-## Step 5 — Test
-
-```bash
-minipostiz auth verify --platform facebook
-minipostiz publish --platform facebook --message "Hello from minipostiz-cli"
-```
-
----
-
-## Troubleshooting
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `190 Invalid OAuth access token` | Token expired or wrong type | Regenerate — ensure you clicked **Generate Access Token** (not "Get App Token") and switched to the **Page** token |
-| `283 Requires pages_read_engagement` | Missing permission on token | Re-generate token with `pages_read_engagement` added; ensure use case is configured in app dashboard |
-| `200 Permission error` | Missing `pages_manage_posts` | Add permission via use case customization in app dashboard |
-| `100 Object does not exist` | Token is a User token, not Page token | Switch to Page in the User/Page dropdown in Graph Explorer |
-| `368 Blocked` | Page or account restricted | Check Page Quality in Facebook Business Suite |
-
-## Token lifetime
-
-- **Short-lived Page Token:** ~1-2 hours
-- **Long-lived Page Token:** ~60 days (use the exchange flow above)
-- **Never-expiring Page Token:** possible for some page roles — check Meta docs
-
-## Re-generating tokens
-
-When your token expires, repeat Step 3 (Graph API Explorer) and update:
-```bash
-minipostiz auth --platform facebook \
-  --pageAccessToken "NEW_TOKEN" \
-  --pageId "YOUR_PAGE_ID"
-```

package/plugins/minipostiz-cli/skills/linkedin-setup/SKILL.md

@@ -1,183 +0,0 @@
----
-name: minipostiz-linkedin-setup
-description: Full LinkedIn OAuth setup for minipostiz-cli — creates app, gets access token + personUrn, stores credentials
-type: setup
----
-
-# minipostiz-cli — LinkedIn Setup
-
-End-to-end guide to get a working LinkedIn access token and store it in minipostiz-cli.
-Covers app creation, product activation, OAuth flow, and credential storage.
-
-## What you need
-
-| Credential | Source |
-|------------|--------|
-| `accessToken` | OAuth 2.0 flow (60-day TTL) |
-| `personUrn` | auto-resolved from token via `/v2/userinfo` if `openid` scope included |
-
----
-
-## Step 1 — LinkedIn Developer App
-
-1. Go to https://www.linkedin.com/developers/apps → **Create app**
-2. Fill in app name, company page, logo → submit
-3. In the app → **Products** tab → request both:
-   - **Share on LinkedIn** → grants `w_member_social` (posting)
-   - **Sign In with LinkedIn using OpenID Connect** → grants `openid profile email` (personUrn resolution)
-4. In **Auth** tab → add redirect URI: `http://localhost:3001`
-5. Note your **Client ID** and **Client Secret**
-
-> Both products are usually auto-approved for developer apps within seconds.
-
----
-
-## Step 2 — Run the OAuth server
-
-Create and run `/tmp/linkedin-oauth-minipostiz.js`:
-
-```javascript
-#!/usr/bin/env node
-const http = require('http');
-const url = require('url');
-const crypto = require('crypto');
-
-const CLIENT_ID = 'YOUR_CLIENT_ID';
-const CLIENT_SECRET = 'YOUR_CLIENT_SECRET';
-const REDIRECT_URI = 'http://localhost:3001';
-const SCOPE = 'w_member_social openid profile email';
-const STATE = crypto.randomBytes(16).toString('hex');
-
-const authUrl = `https://www.linkedin.com/oauth/v2/authorization?` +
-  new URLSearchParams({ response_type: 'code', client_id: CLIENT_ID,
-    redirect_uri: REDIRECT_URI, state: STATE, scope: SCOPE }).toString();
-
-console.log('\n=== LinkedIn OAuth for minipostiz-cli ===');
-console.log('\nOpen this URL in your browser:\n');
-console.log(authUrl);
-console.log('\nWaiting for callback on http://localhost:3001 ...\n');
-
-const server = http.createServer(async (req, res) => {
-  const { pathname, query } = url.parse(req.url, true);
-  if (pathname !== '/') { res.writeHead(404); res.end(); return; }
-
-  const { code, state, error } = query;
-  if (error) { console.error('Auth error:', error); res.end(`<h1>Error: ${error}</h1>`); server.close(); return; }
-  if (state !== STATE) { console.error('State mismatch'); res.end('<h1>State mismatch</h1>'); server.close(); return; }
-
-  // Exchange code for token
-  const tokenRes = await fetch('https://www.linkedin.com/oauth/v2/accessToken', {
-    method: 'POST',
-    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
-    body: new URLSearchParams({ grant_type: 'authorization_code', code,
-      redirect_uri: REDIRECT_URI, client_id: CLIENT_ID, client_secret: CLIENT_SECRET }).toString()
-  });
-  const token = await tokenRes.json();
-
-  if (!token.access_token) {
-    console.error('Token exchange failed:', JSON.stringify(token));
-    res.end('<h1>Token exchange failed — check terminal</h1>');
-    server.close(); return;
-  }
-
-  console.log('\n✓ Access token obtained');
-  console.log('Access Token:', token.access_token);
-  console.log('Expires in:', token.expires_in, 'seconds (~60 days)');
-
-  // Resolve personUrn via userinfo
-  const uiRes = await fetch('https://api.linkedin.com/v2/userinfo', {
-    headers: { Authorization: `Bearer ${token.access_token}` }
-  });
-  const ui = await uiRes.json();
-  const personUrn = ui.sub ? `urn:li:person:${ui.sub}` : null;
-
-  if (personUrn) {
-    console.log('Person URN:', personUrn);
-    console.log('Name:', ui.name);
-  }
-
-  // Write results to tmp files
-  const fs = require('fs');
-  fs.writeFileSync('/tmp/linkedin-access-token.txt', token.access_token);
-  if (personUrn) fs.writeFileSync('/tmp/linkedin-person-urn.txt', personUrn);
-
-  console.log('\n=== minipostiz-cli auth command ===');
-  console.log(`minipostiz auth --platform linkedin --accessToken "${token.access_token}" --personUrn "${personUrn || 'RESOLVE_MANUALLY'}"`);
-  console.log('\n=== or via supercli ===');
-  console.log(`sc minipostiz auth set-linkedin --accessToken "${token.access_token}"${personUrn ? ` --personUrn "${personUrn}"` : ''}`);
-
-  res.writeHead(200, { 'Content-Type': 'text/html' });
-  res.end(`<h1>✓ LinkedIn auth complete</h1>
-    <p><b>Name:</b> ${ui.name || 'N/A'}</p>
-    <p><b>Person URN:</b> ${personUrn || 'not resolved'}</p>
-    <p>Check your terminal for the minipostiz-cli command. You can close this tab.</p>`);
-  server.close();
-});
-
-server.listen(3001);
-process.on('SIGINT', () => { server.close(); process.exit(0); });
-```
-
-**Run it:**
-```bash
-node /tmp/linkedin-oauth-minipostiz.js
-```
-
----
-
-## Step 3 — Store credentials in minipostiz-cli
-
-The script prints the exact command. Run it:
-
-```bash
-# Direct binary
-minipostiz auth --platform linkedin \
-  --accessToken "$(cat /tmp/linkedin-access-token.txt)" \
-  --personUrn "$(cat /tmp/linkedin-person-urn.txt)"
-
-# Or via supercli
-sc minipostiz auth set-linkedin \
-  --accessToken "$(cat /tmp/linkedin-access-token.txt)"
-# (personUrn auto-resolved at post time if openid scope was included)
-```
-
----
-
-## Step 4 — Verify and test
-
-```bash
-# Verify credentials are valid
-minipostiz auth verify --platform linkedin
-
-# Fire a test post
-minipostiz publish --platform linkedin --message "LinkedIn API test via minipostiz-cli"
-
-# Check history
-minipostiz history --platform linkedin --limit 5
-```
-
----
-
-## Step 5 — Cleanup
-
-```bash
-rm /tmp/linkedin-oauth-minipostiz.js /tmp/linkedin-access-token.txt /tmp/linkedin-person-urn.txt
-```
-
----
-
-## Troubleshooting
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `invalid_scope` | App missing required product | Add "Share on LinkedIn" + "Sign In with OpenID" in Products tab |
-| `redirect_uri_mismatch` | URI not registered | Add `http://localhost:3001` in Auth tab → OAuth 2.0 settings |
-| `403 ugcPosts.CREATE` | Token missing `w_member_social` | Re-run OAuth — scope must include `w_member_social` |
-| `Token Type: undefined` | Exchange response parsing bug | Use the Node.js script above — captures full response |
-| personUrn not resolved | Token has no `openid` scope | Re-run with `openid profile email` included in scope |
-
-## Token lifetime
-
-- Expires in **60 days** (5,184,000 seconds)
-- No refresh token in standard OAuth — re-run the flow before expiry
-- Re-run: `node /tmp/linkedin-oauth-minipostiz.js` → paste new token via `minipostiz auth --platform linkedin ...`