atris 2.3.5 → 2.3.8

package/atris/skills/clawhub/atris/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: atris
-description: Codebase intelligence — generates structured navigation maps with file:line references so agents stop re-scanning the same files every session. Use when exploring code, answering "where is X?", or onboarding to a new codebase.
+description: "Codebase intelligence — generates structured navigation maps with file:line references so agents stop re-scanning the same files every session. Use when exploring code, answering 'where is X?', or onboarding to a new codebase."
 version: 1.1.0
 requires:
   bins:

package/atris/skills/create-member/SKILL.md

@@ -0,0 +1,248 @@
+---
+name: create-member
+description: "Create and manage AI team members using the MEMBER.md format. Use when the user wants to define a new AI role, set up a team member, create an agent persona, or work with team/MEMBER.md files."
+version: 1.0.0
+tags:
+  - team
+  - member
+  - agent
+  - persona
+---
+
+# Member Creator
+
+Create AI team members using the MEMBER.md format. A member is a directory that bundles persona, skills, tools, and context into a deployable AI worker.
+
+## What is MEMBER.md
+
+MEMBER.md defines a complete AI team member. It composes existing standards (SKILL.md for capabilities, .mcp.json for tool servers) into a single portable unit.
+
+Spec: https://github.com/atrislabs/member
+
+## Directory Structure
+
+```
+team/<name>/
+├── MEMBER.md       REQUIRED  Persona + role + permissions
+├── skills/         OPTIONAL  SKILL.md files (capabilities)
+│   └── <skill>/
+│       └── SKILL.md
+├── tools/          OPTIONAL  MCP servers, API docs, CLI docs
+│   ├── .mcp.json
+│   └── <tool>.md
+└── context/        OPTIONAL  Domain knowledge (markdown)
+    └── *.md
+```
+
+## Creating a Member
+
+When the user asks to create a team member, follow these steps:
+
+### Step 1: Ask what role
+
+Ask the user:
+- What role is this member? (e.g., SDR, support agent, code reviewer)
+- What should they be able to do?
+- What should they NOT be able to do?
+
+### Step 2: Create the directory
+
+```
+team/<name>/
+├── MEMBER.md
+├── skills/
+├── tools/
+└── context/
+```
+
+Use kebab-case for the name. Create all four directories even if empty.
+
+### Step 3: Write MEMBER.md
+
+Use this structure:
+
+```yaml
+---
+name: <kebab-case-name>
+role: <Human Readable Title>
+description: <one line — what this member does>
+version: 1.0.0
+
+skills: []
+
+permissions:
+  can-read: true
+---
+```
+
+Below the frontmatter, write three sections:
+
+**Persona** — How the member communicates. Tone, style, decision-making approach. Be specific — "direct and research-driven" is better than "professional and helpful."
+
+**Workflow** — Numbered steps the member follows. This is the core operating procedure. Each step should be a concrete action.
+
+**Rules** — Hard constraints. What the member must always or never do. Keep it to 3-5 rules.
+
+### Step 4: Add permissions
+
+Common permission patterns:
+
+```yaml
+# Read-only member (planner, researcher)
+permissions:
+  can-read: true
+  can-execute: false
+
+# Builder with guardrails
+permissions:
+  can-read: true
+  can-execute: true
+  can-delete: false
+  approval-required: [delete, deploy]
+
+# Full access (reviewer, admin)
+permissions:
+  can-read: true
+  can-execute: true
+  can-approve: true
+  can-ship: true
+```
+
+Permissions are declarations, not enforcement. They tell the agent what its boundaries are. The agent respects them because they're in its instructions.
+
+### Step 5: Add skills (optional)
+
+If the member needs specific capabilities, create SKILL.md files:
+
+```
+team/<name>/skills/<skill-name>/SKILL.md
+```
+
+Each skill follows the standard SKILL.md format:
+
+```yaml
+---
+name: <skill-name>
+description: <what this skill does>
+---
+
+# <Skill Name>
+
+<Instructions for how to perform this capability>
+```
+
+Update the member's frontmatter to list the skill:
+
+```yaml
+skills:
+  - <skill-name>
+```
+
+### Step 6: Add context (optional)
+
+Drop markdown files into `context/` with domain knowledge the member needs:
+- Playbooks, SOPs, guidelines
+- Customer profiles, ICPs
+- Reference docs, templates
+
+No special format. Just markdown files the member references.
+
+## Flat File Format
+
+For simple members that just need a persona (no skills, tools, or context), use a flat file:
+
+```
+team/<name>.md
+```
+
+Same frontmatter, same format. Just no directory structure around it.
+
+## Detection
+
+Add to your project's CLAUDE.md (or AGENTS.md for Codex):
+
+```markdown
+## Team
+
+This project uses MEMBER.md team members in `team/`.
+When activated as a specific member, read `team/<name>/MEMBER.md`.
+```
+
+## Multi-Agent Usage
+
+Activate different members for different tasks:
+
+```
+"Act as the navigator. Read team/navigator/MEMBER.md and plan this feature."
+"Act as the validator. Read team/validator/MEMBER.md and review these changes."
+```
+
+Each member gets its own persona, skills, permissions, and context.
+
+## Examples
+
+### Dev team member (code reviewer)
+
+```yaml
+---
+name: reviewer
+role: Code Reviewer
+description: Reviews PRs for correctness, security, and style
+version: 1.0.0
+skills: []
+permissions:
+  can-read: true
+  can-approve: true
+  can-execute: false
+---
+
+## Persona
+Thorough but not pedantic. You catch real bugs, not style nits.
+If something works and is readable, approve it.
+
+## Workflow
+1. Read the diff
+2. Check for bugs, security issues, breaking changes
+3. Approve or request specific changes (no vague feedback)
+
+## Rules
+1. Never block on style alone
+2. Every comment must be actionable
+3. If unsure, approve with a note
+```
+
+### Business role (SDR)
+
+```yaml
+---
+name: sdr
+role: Sales Development Rep
+description: Outbound prospecting and lead qualification
+version: 1.0.0
+skills:
+  - email-outreach
+  - lead-research
+permissions:
+  can-draft: true
+  can-send: false
+  approval-required: [send, delete]
+tools:
+  - hubspot
+  - apollo
+---
+
+## Persona
+Research-driven. Every email references something specific about
+the prospect. If you can't find a hook, don't send.
+
+## Workflow
+1. Research the lead
+2. Qualify against ICP (context/icp.md)
+3. Draft personalized sequence
+4. Flag for human approval
+
+## Rules
+1. Never send without approval
+2. Every email must reference something specific
+3. Log everything to CRM
+```

package/atris/skills/drive/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: drive
 description: Google Drive integration via AtrisOS API. Browse, search, read, upload files and work with Google Sheets. Use when user asks about Drive, files, docs, sheets, or spreadsheets.
-version: 1.1.0
+version: 1.2.0
 tags:
   - drive
   - backend
@@ -199,6 +199,29 @@ curl -s -X POST "https://api.atris.ai/api/integrations/google-drive/files" \
   }'
 ```
 
+### Update Existing File
+```bash
+curl -s -X PUT "https://api.atris.ai/api/integrations/google-drive/files/{file_id}" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "content": "Updated file content here",
+    "mime_type": "text/plain"
+  }'
+```
+
+**Update content and rename:**
+```bash
+curl -s -X PUT "https://api.atris.ai/api/integrations/google-drive/files/{file_id}" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "content": "New content",
+    "mime_type": "text/plain",
+    "name": "renamed-file.txt"
+  }'
+```
+
 ---
 
 ## Google Sheets
@@ -299,6 +322,14 @@ curl -s -X POST "https://api.atris.ai/api/integrations/google-drive/sheets/{spre
 3. **Confirm with user**: "Upload {filename} to Drive?"
 4. Upload: `POST /google-drive/files` with `{name, content, mime_type}`
 
+### "Edit a file on Drive"
+1. Run bootstrap
+2. Find the file: `GET /google-drive/search?q=FILENAME`
+3. Read current content: `GET /google-drive/files/{id}/export?mime_type=text/plain`
+4. Make edits
+5. **Show user the changes for approval**
+6. Update: `PUT /google-drive/files/{id}` with `{content, mime_type}`
+
 ---
 
 ## Error Handling
@@ -356,8 +387,13 @@ curl -s -X POST "https://api.atris.ai/api/integrations/google-drive/sheets/{id}/
   -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
   -d '{"range":"Sheet1","values":[["Alice",95]]}'
 
-# Upload a file
+# Upload a new file
 curl -s -X POST "https://api.atris.ai/api/integrations/google-drive/files" \
   -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
   -d '{"name":"notes.txt","content":"Hello world","mime_type":"text/plain"}'
+
+# Update an existing file
+curl -s -X PUT "https://api.atris.ai/api/integrations/google-drive/files/{file_id}" \
+  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
+  -d '{"content":"Updated content","mime_type":"text/plain"}'
 ```

package/atris/skills/email-agent/SKILL.md

@@ -250,6 +250,17 @@ curl -s -X DELETE "https://api.atris.ai/api/integrations/gmail/drafts/{draft_id}
   -H "Authorization: Bearer $TOKEN"
 ```
 
+### Mark as Read / Unread
+```bash
+# Mark as read
+curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/{message_id}/read" \
+  -H "Authorization: Bearer $TOKEN"
+
+# Mark as unread
+curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/{message_id}/unread" \
+  -H "Authorization: Bearer $TOKEN"
+```
+
 ### Archive Email
 ```bash
 # Single message
@@ -263,6 +274,19 @@ curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/batch-arch
   -d '{"message_ids": ["id1", "id2", "id3"]}'
 ```
 
+### Trash Email
+```bash
+# Single message
+curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/{message_id}/trash" \
+  -H "Authorization: Bearer $TOKEN"
+
+# Batch trash
+curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/batch-trash" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"message_ids": ["id1", "id2", "id3"]}'
+```
+
 ### Check Status
 ```bash
 curl -s "https://api.atris.ai/api/integrations/gmail/status" \
@@ -410,6 +434,12 @@ curl -s -X POST "https://api.atris.ai/api/integrations/gmail/drafts" \
   -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
   -d '{"to":"email@example.com","subject":"Hi","body":"Draft text"}'
 
+# Mark as read
+curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/{message_id}/read" -H "Authorization: Bearer $TOKEN"
+
+# Trash an email
+curl -s -X POST "https://api.atris.ai/api/integrations/gmail/messages/{message_id}/trash" -H "Authorization: Bearer $TOKEN"
+
 # Send a draft
 curl -s -X POST "https://api.atris.ai/api/integrations/gmail/drafts/{draft_id}/send" \
   -H "Authorization: Bearer $TOKEN"

package/atris/skills/slack/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: slack
 description: Slack integration via AtrisOS API. Read messages, send as yourself, search conversations, manage DMs. Use when user asks about Slack, messages, channels, or team communication.
-version: 1.0.0
+version: 1.1.0
 tags:
   - slack
   - backend
@@ -187,6 +187,14 @@ curl -s "https://api.atris.ai/api/integrations/slack/users" \
   -H "Authorization: Bearer $TOKEN"
 ```
 
+### Search Users
+```bash
+curl -s "https://api.atris.ai/api/integrations/slack/users/search?q=justin" \
+  -H "Authorization: Bearer $TOKEN"
+```
+
+Searches by name, display name, or email. Much faster than pulling the full user list.
+
 ### Send as Bot
 ```bash
 curl -s -X POST "https://api.atris.ai/api/integrations/slack/test-send" \
@@ -223,9 +231,9 @@ curl -s -X DELETE "https://api.atris.ai/api/integrations/slack" \
 
 ### "Send a message to someone"
 1. Run bootstrap
-2. Find the user: `GET /slack/users` (search by name/email)
+2. Find the user: `GET /slack/users/search?q=NAME`
 3. **Show user the draft for approval**
-4. Send DM: `POST /slack/me/dm` with `{user_id, text}`
+4. Send DM: `POST /slack/me/dm` with `{slack_user_id, text}`
 5. Confirm: "Message sent!"
 
 ### "Reply in a channel"
@@ -243,7 +251,7 @@ curl -s -X DELETE "https://api.atris.ai/api/integrations/slack" \
 
 ### "What did [person] say to me?"
 1. Run bootstrap
-2. List users: `GET /slack/users` (find user ID)
+2. Find user: `GET /slack/users/search?q=NAME` (get user ID)
 3. List DMs: `GET /slack/me/dms` (find DM channel with that user)
 4. Read messages: `GET /slack/me/messages/{channel_id}`
 5. Display conversation
@@ -317,4 +325,7 @@ curl -s "https://api.atris.ai/api/integrations/slack/me/search?q=project+update"
 
 # List workspace users
 curl -s "https://api.atris.ai/api/integrations/slack/users" -H "Authorization: Bearer $TOKEN"
+
+# Search users by name
+curl -s "https://api.atris.ai/api/integrations/slack/users/search?q=justin" -H "Authorization: Bearer $TOKEN"
 ```

package/atris/skills/x-search/SKILL.md

@@ -0,0 +1,234 @@
+---
+name: x-search
+description: "X/Twitter search via xAI Grok API. Use when user wants to search tweets, monitor topics, find viral posts, or run social listening. Costs 5 credits per search. Triggers on x search, tweet search, twitter search, social listening, revenue intel, viral tweets."
+version: 2.0.0
+tags:
+  - x-search
+  - social
+  - research
+---
+
+# X Search
+
+> Drop this in `~/.claude/skills/x-search/SKILL.md` and Claude Code becomes your X/Twitter intelligence tool.
+
+## Bootstrap (ALWAYS Run First)
+
+Before any X search operation, run this bootstrap to ensure everything is set up:
+
+```bash
+#!/bin/bash
+set -e
+
+# 1. Check if atris CLI is installed
+if ! command -v atris &> /dev/null; then
+  echo "Installing atris CLI..."
+  npm install -g atris
+fi
+
+# 2. Check if logged in to AtrisOS
+if [ ! -f ~/.atris/credentials.json ]; then
+  echo "Not logged in to AtrisOS."
+  echo ""
+  echo "Option 1 (interactive): Run 'atris login' and follow prompts"
+  echo "Option 2 (non-interactive): Get token from https://atris.ai/auth/cli"
+  echo "                           Then run: atris login --token YOUR_TOKEN"
+  echo ""
+  exit 1
+fi
+
+# 3. Extract token
+if command -v node &> /dev/null; then
+  TOKEN=$(node -e "console.log(require('$HOME/.atris/credentials.json').token)")
+elif command -v python3 &> /dev/null; then
+  TOKEN=$(python3 -c "import json,os; print(json.load(open(os.path.expanduser('~/.atris/credentials.json')))['token'])")
+elif command -v jq &> /dev/null; then
+  TOKEN=$(jq -r '.token' ~/.atris/credentials.json)
+else
+  echo "Error: Need node, python3, or jq to read credentials"
+  exit 1
+fi
+
+# 4. Quick auth check
+STATUS=$(curl -s "https://api.atris.ai/api/me" \
+  -H "Authorization: Bearer $TOKEN")
+
+if echo "$STATUS" | grep -q "Token expired\|Not authenticated\|Unauthorized"; then
+  echo "Token expired. Please re-authenticate:"
+  echo "  Run: atris login --force"
+  exit 1
+fi
+
+echo "Ready. X Search is available (5 credits per search)."
+export ATRIS_TOKEN="$TOKEN"
+```
+
+---
+
+## API Reference
+
+Base: `https://api.atris.ai/api/x-search`
+
+All requests require: `-H "Authorization: Bearer $TOKEN"`
+
+### Get Token (after bootstrap)
+```bash
+TOKEN=$(node -e "console.log(require('$HOME/.atris/credentials.json').token)")
+```
+
+### Search X/Twitter
+```bash
+curl -s -X POST "https://api.atris.ai/api/x-search/search" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "query": "\"CRM is dead\" OR \"Salesforce alternative\"",
+    "limit": 10
+  }'
+```
+
+**With date filter** (last N days only):
+```bash
+curl -s -X POST "https://api.atris.ai/api/x-search/search" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "query": "AI agents replacing SaaS",
+    "limit": 10,
+    "days_back": 7
+  }'
+```
+
+**Response:**
+```json
+{
+  "status": "success",
+  "credits_used": 5,
+  "credits_remaining": 995,
+  "data": {
+    "content": "1. @levelsio: AI agents are replacing...",
+    "citations": ["https://x.com/levelsio/status/..."],
+    "usage": {"prompt_tokens": 200, "completion_tokens": 800}
+  }
+}
+```
+
+### Research a Person
+```bash
+curl -s -X POST "https://api.atris.ai/api/x-search/research-person" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "Leah Bonvissuto",
+    "handle": "leahbon",
+    "company": "Presentr",
+    "context": "Interested in revenue intelligence and AI for GTM"
+  }'
+```
+
+**Response:**
+```json
+{
+  "status": "success",
+  "credits_used": 5,
+  "credits_remaining": 990,
+  "data": {
+    "content": "### 1. Profile\n**Name:** Leah Bonvissuto\n...",
+    "citations": ["https://x.com/..."],
+    "usage": {"prompt_tokens": 300, "completion_tokens": 1200}
+  }
+}
+```
+
+---
+
+## Workflows
+
+### "Search X for tweets about a topic"
+1. Run bootstrap
+2. Search: `POST /x-search/search` with `{query, limit}`
+3. Display results: tweet text, author, engagement, links
+
+### "Find tweets from the last week about X"
+1. Run bootstrap
+2. Search with date filter: `POST /x-search/search` with `{query, limit, days_back: 7}`
+3. Display results sorted by engagement
+
+### "Research a person before a meeting"
+1. Run bootstrap
+2. Research: `POST /x-search/research-person` with `{name, handle, company, context}`
+3. Display profile, background, talking points
+
+### "Monitor keyword clusters for revenue intel"
+1. Run bootstrap
+2. Run multiple searches across keyword clusters:
+   - `"CRM is dead" OR "Salesforce is dead" OR "HubSpot sucks"`
+   - `"revenue operations" (broken OR frustrated OR replacing)`
+   - `(founder OR CEO) "tech stack" (consolidating OR ripping out)`
+3. Each search costs 5 credits
+4. Combine results, rank by engagement, draft replies
+
+### "Find viral tweets in my industry"
+1. Run bootstrap
+2. Search with engagement filter: `POST /x-search/search` with query including `min_faves:50`
+3. Display top tweets sorted by likes/retweets
+
+---
+
+## Query Tips
+
+| Goal | Query Example |
+|------|--------------|
+| Specific phrase | `"revenue operations"` |
+| OR logic | `"CRM is dead" OR "Salesforce alternative"` |
+| From a user | `from:levelsio` |
+| High engagement | `"AI agents" min_faves:50` |
+| Exclude retweets | `"your query" -is:retweet` |
+| Multiple keywords | `(founder OR CEO) ("AI adoption" OR "AI native")` |
+
+---
+
+## Billing
+
+- Every search costs **5 credits** (flat)
+- 1 credit = $0.01, so 1 search = $0.05
+- Research person also costs 5 credits
+- Credits are deducted server-side before the search runs
+- If insufficient credits, returns `402 Insufficient credits`
+
+---
+
+## Error Handling
+
+| Error | Meaning | Solution |
+|-------|---------|----------|
+| `401 Not authenticated` | Invalid/expired token | Run `atris login` |
+| `402 Insufficient credits` | Not enough credits | Purchase credits at atris.ai |
+| `502 Search failed` | xAI API issue | Retry in a few seconds |
+
+---
+
+## Quick Reference
+
+```bash
+# Setup (one time)
+npm install -g atris && atris login
+
+# Get token
+TOKEN=$(node -e "console.log(require('$HOME/.atris/credentials.json').token)")
+
+# Search tweets
+curl -s -X POST "https://api.atris.ai/api/x-search/search" \
+  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
+  -d '{"query": "AI agents", "limit": 10}'
+
+# Search last 7 days only
+curl -s -X POST "https://api.atris.ai/api/x-search/search" \
+  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
+  -d '{"query": "AI agents", "limit": 10, "days_back": 7}'
+
+# Research a person
+curl -s -X POST "https://api.atris.ai/api/x-search/research-person" \
+  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
+  -d '{"name": "John Doe", "handle": "johndoe", "company": "Acme"}'
+```