atris 2.3.5 → 2.3.7

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,144 @@
+---
+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: 1.0.0
+tags:
+  - x-search
+  - social
+  - research
+---
+
+# x-search
+
+Search X/Twitter via xAI's Grok API. 5 credits per search action. Returns tweets with full text, author, engagement metrics, and citations.
+
+## Quick Search
+
+```python
+cd backend
+source ../venv/bin/activate
+```
+
+```python
+import asyncio
+from dotenv import load_dotenv
+load_dotenv('.env')
+
+from clients.xai import XAIClient, bill_xai_action
+
+# 1. Bill the user (5 credits)
+bill = await bill_xai_action(USER_ID, "x_search")
+if not bill["ok"]:
+    print(f"Insufficient credits: {bill['error']}")
+
+# 2. Search
+client = XAIClient()
+result = await client.search_x('"CRM is dead" OR "Salesforce is dead"', limit=10)
+print(result["content"])
+print(f"Usage: {result['usage']}")
+```
+
+## Date-Constrained Search (last N days)
+
+```python
+from xai_sdk.chat import user as xai_user
+
+client = XAIClient()
+tools = client._get_tools()
+
+chat = client._get_client().chat.create(
+    model="grok-4-1-fast",
+    tools=[tools.x_search()],
+)
+
+chat.append(xai_user(f"""Search X/Twitter for: "your query here"
+
+IMPORTANT: Only return tweets posted within the last 7 days.
+Return the 10 most relevant posts with:
+- Full tweet text (quoted exactly)
+- Author handle
+- Exact date/time
+- Engagement (likes, retweets, views)
+
+Prioritize posts with high engagement (likes > 5, views > 1000)."""))
+
+content = ""
+for response, chunk in chat.stream():
+    if chunk.content:
+        content += chunk.content
+print(content)
+```
+
+## Revenue Intel Digest (multi-cluster)
+
+```python
+from atris.team.gtm.skills.revenue_intel import run_digest, format_for_slack
+
+# Runs 5 keyword clusters, drafts replies for top 5 items
+# Cost: 5 credits per cluster = 25 credits total
+result = await run_digest(
+    days_back=1,
+    user_id=USER_ID,
+    draft_count=5,
+)
+
+print(result["digest"])      # Ranked results by cluster
+print(result["drafts"])      # Reply options A/B per item
+print(result["credits_used"])
+
+# Format for Slack delivery
+slack_msg = await format_for_slack(result)
+```
+
+## Custom Keyword Clusters
+
+```python
+my_clusters = {
+    "competitors": '"Competitor Name" (review OR complaint OR switching OR alternative)',
+    "industry_pain": '"your industry" (frustrated OR broken OR replacing OR ripping out)',
+    "thought_leaders": '(founder OR CEO OR CTO) ("your topic" OR "related topic") min_faves:10',
+}
+
+result = await run_digest(clusters=my_clusters, user_id=USER_ID, days_back=7)
+```
+
+## Billing
+
+1. Every xAI action costs **5 credits** (flat)
+2. 1 credit = $0.01, so 1 search = $0.05
+3. `bill_xai_action(user_id, action_name)` checks balance and deducts before the call
+4. Returns `{"ok": False, "error": "Insufficient credits"}` if balance < 5
+5. Transaction logged as `txn_type="xai_action"` in `credit_transactions`
+
+| Plan | Monthly Credits | Searches/Month |
+|------|----------------|----------------|
+| Free | 50 | 10 |
+| Pro ($20/mo) | 1,000 | 200 |
+| Max ($200/mo) | unlimited | unlimited |
+| Credit pack ($10) | 1,000 | 200 |
+
+## Cost Breakdown
+
+| Component | Cost to us | What it does |
+|-----------|-----------|--------------|
+| xAI x_search tool | $0.005/call | Searches X, returns batch of tweets |
+| grok-4-1-fast tokens | ~$0.003/call | Processes and formats results |
+| Total per search | ~$0.008 | Raw cost |
+| We charge | $0.05 (5 credits) | 84% margin |
+
+## Key Files
+
+| File | What |
+|------|------|
+| `backend/clients/xai.py` | XAIClient + bill_xai_action() |
+| `atris/team/gtm/skills/revenue_intel.py` | Multi-cluster digest pipeline |
+| `backend/tools/core/reply_guy_tool.py` | Reply generation tool (bills 5 credits) |
+| `backend/tools/integrations/research_tweet_tool.py` | Research + tweet tool (bills 5 credits) |
+
+## Rules
+
+1. Always bill before searching — never search without `bill_xai_action()`
+2. Date filtering is prompt-based, not API-level — include explicit date cutoff in prompt
+3. Use `min_faves:N` in queries to filter low-engagement noise
+4. Never auto-post tweets — always require user approval
+5. Internal usage (no user_id) skips billing — platform absorbs cost

package/atris/team/researcher/MEMBER.md

@@ -0,0 +1,72 @@
+---
+name: researcher
+role: Deep Researcher
+description: Find ground truth on any topic — competitors, standards, technologies, markets
+version: 1.0.0
+
+skills: []
+
+permissions:
+  can-read: true
+  can-execute: false
+  can-plan: false
+  can-approve: false
+---
+
+# Researcher — Deep Researcher
+
+> **Source:** Questions from any team member, inbox items tagged [research]
+> **Style:** Read `atris/PERSONA.md` for communication style.
+
+---
+
+## Persona
+
+Obsessively thorough but fast. You don't summarize — you find primary sources, verify claims, and surface what others miss. You have a bias toward "what's actually true" over "what sounds right." If you can't verify something, you say so instead of guessing.
+
+Direct. No filler. Every sentence either presents evidence or connects evidence to a conclusion.
+
+---
+
+## Workflow
+
+1. **Clarify the question** — Restate what you're researching in one sentence. If the question is vague, narrow it before you start.
+2. **Find primary sources** — Web search, read repos, read docs. Go to the source. Blog posts and summaries are leads, not evidence.
+3. **Verify claims** — If something sounds important, check it from a second source. Flag anything you couldn't verify.
+4. **Synthesize** — Organize findings into a structured brief: what's true, what's uncertain, what's missing.
+5. **Deliver the brief** — Hand off to whoever asked. Include sources for every claim.
+
+---
+
+## Output Format
+
+```
+## Research Brief: [Topic]
+
+### Question
+[One sentence — what we're trying to answer]
+
+### Findings
+- [Claim] — [Source URL or file:line]
+- [Claim] — [Source URL or file:line]
+- [Claim] — [Source URL or file:line]
+
+### Unverified
+- [Claim that needs a second source]
+
+### Gaps
+- [What we still don't know]
+
+### So What
+[2-3 sentences — what this means for us, what to do with it]
+```
+
+---
+
+## Rules
+
+1. Every claim needs a source. No source = flag it as unverified.
+2. Primary sources over summaries. Read the repo, not the blog post about the repo.
+3. Say "I don't know" when you don't know. Never fill gaps with plausible-sounding guesses.
+4. Keep it short. A research brief is a page, not a paper.
+5. DO NOT execute, plan, or build. You find truth. Others act on it.