@devrev-computer/skills 1.0.0

package/README.md

@@ -0,0 +1,37 @@
+# computer-skill
+
+AI-powered skills for Claude Code — sales intelligence, deal management, workflow automation, and agent debugging, built on DevRev.
+
+## Skills
+
+| Skill | Description |
+|-------|-------------|
+| **create-workflow-template** | Generate DevRev workflow template JSON from natural language descriptions |
+| **deal-review-meddpicc** | Full MEDDPICC deal assessment with evidence-tagged scoring |
+| **sales-call-plan-coach** | Interactive call plan coaching using Franklin Covey methodology |
+| **account-evaluation** | Account health report combining DevRev pipeline, engagement, and external data |
+| **account-research** | Company/person research — web + DevRev + enrichment layers |
+| **customer-brief** | Pre-meeting briefing with internal intelligence and external context |
+| **sales-search-and-lookup** | Query pipeline, forecast, accounts, and opportunities via natural language |
+| **sales-context** | Always-active behavioral skill for consistent sales terminology |
+| **next-step-for-opportunity** | Extract planned actions from meetings, emails, and discussions |
+| **trace-diagnosis** | Debug Computer agent execution traces and auto-create engineering tickets |
+
+## Setup
+
+Copy any skill folder into your project's `.claude/skills/` directory:
+
+```bash
+mkdir -p .claude/skills
+cp -r <skill-name> .claude/skills/
+```
+
+Or install with the skills CLI:
+
+```bash
+npx skills add https://github.com/shashankcube/computer-skill --skill <skill-name>
+```
+
+## License
+
+Based on [DevRev Computer Skills](https://github.com/devrev/computer-skills).

package/bin/install.mjs

@@ -0,0 +1,158 @@
+#!/usr/bin/env node
+
+import { readdir, cp, mkdir, stat, readFile } from "node:fs/promises";
+import { join, dirname } from "node:path";
+import { fileURLToPath } from "node:url";
+import { parseArgs } from "node:util";
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const skillsSource = join(__dirname, "..", "skills");
+
+const SKILLS = [
+  "account-evaluation",
+  "account-research",
+  "create-workflow-template",
+  "customer-brief",
+  "deal-review-meddpicc",
+  "next-step-for-opportunity",
+  "opportunity-feature-prioritizer",
+  "sales-call-plan-coach",
+  "sales-context",
+  "sales-search-and-lookup",
+  "skill-creator",
+  "trace-diagnosis",
+];
+
+function usage() {
+  console.log(`
+Usage: computer-skills [options]
+
+Install DevRev Computer Skills into your project's .claude/skills/ directory.
+
+Options:
+  --list, -l          List available skills
+  --skill, -s <name>  Install specific skill(s) (repeatable)
+  --dir, -d <path>    Target project directory (default: cwd)
+  --uninstall, -u     Remove installed skills
+  --help, -h          Show this help
+`);
+}
+
+async function getSkillDescription(skillDir) {
+  const candidates = [
+    "SKILL.md",
+    ...SKILLS.map((s) => `${s}.md`),
+  ];
+  for (const file of await readdir(skillDir)) {
+    if (file.endsWith(".md") && (file === "SKILL.md" || file === join(skillDir).split("/").pop() + ".md")) {
+      try {
+        const content = await readFile(join(skillDir, file), "utf-8");
+        const match = content.match(/description:\s*>?\s*\n?\s*(.+)/);
+        if (match) return match[1].trim().slice(0, 80);
+      } catch {}
+    }
+  }
+  return "";
+}
+
+async function listSkills() {
+  console.log("\nAvailable skills:\n");
+  for (const skill of SKILLS) {
+    const desc = await getSkillDescription(join(skillsSource, skill)).catch(() => "");
+    console.log(`  ${skill}${desc ? ` — ${desc}` : ""}`);
+  }
+  console.log(`\n  ${SKILLS.length} skills total\n`);
+}
+
+async function installSkills(targetDir, selectedSkills) {
+  const skillsDir = join(targetDir, ".claude", "skills");
+  await mkdir(skillsDir, { recursive: true });
+
+  const toInstall = selectedSkills.length > 0 ? selectedSkills : SKILLS;
+  const invalid = toInstall.filter((s) => !SKILLS.includes(s));
+  if (invalid.length > 0) {
+    console.error(`Unknown skill(s): ${invalid.join(", ")}`);
+    console.error(`Run 'computer-skills --list' to see available skills.`);
+    process.exit(1);
+  }
+
+  let installed = 0;
+  let skipped = 0;
+
+  for (const skill of toInstall) {
+    const src = join(skillsSource, skill);
+    const dest = join(skillsDir, skill);
+
+    try {
+      await stat(src);
+    } catch {
+      console.error(`  skip  ${skill} (not found in package)`);
+      skipped++;
+      continue;
+    }
+
+    await cp(src, dest, { recursive: true, force: true });
+    console.log(`  +  ${skill}`);
+    installed++;
+  }
+
+  console.log(
+    `\nInstalled ${installed} skill(s) into ${skillsDir}${skipped > 0 ? ` (${skipped} skipped)` : ""}`
+  );
+}
+
+async function uninstallSkills(targetDir, selectedSkills) {
+  const { rm } = await import("node:fs/promises");
+  const skillsDir = join(targetDir, ".claude", "skills");
+  const toRemove = selectedSkills.length > 0 ? selectedSkills : SKILLS;
+
+  let removed = 0;
+  for (const skill of toRemove) {
+    const dest = join(skillsDir, skill);
+    try {
+      await stat(dest);
+      await rm(dest, { recursive: true, force: true });
+      console.log(`  -  ${skill}`);
+      removed++;
+    } catch {
+      // not installed, skip
+    }
+  }
+  console.log(`\nRemoved ${removed} skill(s) from ${skillsDir}`);
+}
+
+async function main() {
+  const { values } = parseArgs({
+    options: {
+      list: { type: "boolean", short: "l", default: false },
+      skill: { type: "string", short: "s", multiple: true, default: [] },
+      dir: { type: "string", short: "d", default: process.cwd() },
+      uninstall: { type: "boolean", short: "u", default: false },
+      help: { type: "boolean", short: "h", default: false },
+    },
+    strict: true,
+  });
+
+  if (values.help) {
+    usage();
+    process.exit(0);
+  }
+
+  if (values.list) {
+    await listSkills();
+    process.exit(0);
+  }
+
+  console.log("\n@devrev/computer-skills\n");
+
+  if (values.uninstall) {
+    await uninstallSkills(values.dir, values.skill);
+  } else {
+    await installSkills(values.dir, values.skill);
+  }
+}
+
+main().catch((err) => {
+  console.error(err.message);
+  process.exit(1);
+});

package/package.json

@@ -0,0 +1,33 @@
+{
+  "name": "@devrev-computer/skills",
+  "version": "1.0.0",
+  "description": "AI-powered skills for Claude Code — sales intelligence, deal management, workflow automation, and agent debugging, built on DevRev.",
+  "type": "module",
+  "bin": {
+    "computer-skills": "./bin/install.mjs"
+  },
+  "scripts": {
+    "prepare": "node scripts/prepare.mjs",
+    "prepublishOnly": "node scripts/prepare.mjs"
+  },
+  "files": [
+    "bin/",
+    "skills/"
+  ],
+  "keywords": [
+    "claude-code",
+    "skills",
+    "devrev",
+    "sales",
+    "ai"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/shashankcube/computer-skill.git"
+  },
+  "license": "MIT",
+  "author": "DevRev",
+  "engines": {
+    "node": ">=18"
+  }
+}

package/skills/account-evaluation/account-evaluation.md

@@ -0,0 +1,64 @@
+---
+skill-name: account-evaluation
+user-invocable: true
+description: Produce a comprehensive account health report combining internal and external data. Use when user says "evaluate account", "account health", "how is [company] doing", "account summary", or "give me an overview of [account]".
+arguments:
+  - name: account
+    description: The account name, display ID, or DON ID to evaluate
+    required: true
+---
+
+# AccountEvaluation
+
+Produces a comprehensive account health report combining internal and external data.
+
+## Tools
+
+1. **GetKGSchema** — Gets the full knowledge graph schema. Call before any SQL workflow.
+2. **GetNodeSchema** — Gets schema details for a specific node. Make parallel calls for multiple nodes.
+3. **NLToSQL** — Converts natural language to SQL. Never write SQL yourself. Always call before ExecuteSQL.
+4. **ExecuteSQL** — Executes SQL generated by NLToSQL. Always call NLToSQL first.
+5. **FetchObjectContext** — Fetches full object details by DON or display ID.
+6. **HybridSearch** — Semantic search. Use to get object IDs or filter IDs from SQL results. Never use for structured filtering.
+7. **WebSearch** — Search the web for external intelligence about the account.
+8. **MeetingSummaryOpp** — Gets meeting summaries linked to an opportunity.
+9. **EmailSummaryOpp** — Gets email summaries linked to an opportunity.
+
+## Account Disambiguation
+
+Always clarify which account (DON ID) before proceeding. Multiple accounts can share the same display name. If one match found state assumption and proceed. If multiple found list them and ask user to select.
+
+## Data Gathering Sequence
+
+1. HybridSearch to find account by name and get DON ID
+2. FetchObjectContext on account DON: owner, tier, industry, linked contacts
+3. SQL path (GetKGSchema → GetNodeSchema → NLToSQL → ExecuteSQL) for all linked opportunities: display ID, title, stage, annual_recurring_revenue (ACV), amount (TCV), owner, target close date, forecast category, probability. LIMIT 500.
+4. FetchObjectContext on top opportunities (stage 3+, non-duplicate) for discussion threads and activity
+5. MeetingSummaryOpp and EmailSummaryOpp for recent engagement on active opportunities
+6. WebSearch for external intelligence: news, funding, leadership changes, strategic initiatives
+7. Exclude opportunities tagged with closed lost reason duplicate opportunity silently
+
+## Formatting Rules
+
+- Never show raw DON IDs alone. Always pair with human-readable name.
+- Group opportunities: Closed Won, Active Pipeline (stage 3+), Early Stage, Closed Lost
+- Show ACV and TCV as separate columns with subtotals per group
+- Prioritize recent data over older data
+
+## Required Output Sections
+
+1. **Summary**: 3-5 bullet executive summary
+2. **Key Metrics at a Glance**: ARR, TCV, opportunities by stage, account tier, primary owner
+3. **Lines of Business**: products or services the account uses or is evaluating
+4. **Strategic AI Initiatives**: any AI or DevRev-specific initiatives underway or discussed
+5. **Top Priority Pursuits**: active high-value opportunities with stage, ACV, TCV, owner, close date
+6. **Internal Discussions and Product Interest**: themes from discussions and tickets
+7. **Deal Velocity Considerations**: days in stage, stalled deals, close date risk
+8. **Account Status and Engagement**: last touchpoint date, engagement frequency, relationship health
+9. **Recommended Actions Next 30 Days**: 3-5 actions with Who, Pitch, Ask, Timeline
+10. **Recent Momentum**: latest wins, meetings, or positive signals
+11. **Recommended Discussion Topics**: suggested conversation starters
+12. **Conclusion**: 2-3 sentence summary of account health and strategic priority
+13. **References**: DON IDs and external URLs used
+
+Show the SQL query used at the bottom of the response.

package/skills/account-research/account-research.md

@@ -0,0 +1,323 @@
+---
+skill-name: account-research
+description: Research a company or person — combines web search, DevRev internal data, and optional enrichment/CRM. Use when user says "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", "tell me about [company]", or "pull up signals for [account]".
+arguments:
+  - name: target
+    description: Company name, domain, person name, or DevRev account ID to research
+    required: true
+---
+
+# Account Research
+
+Get a complete picture of any company or person before outreach. Combines three data layers — each adds depth but none is required.
+
+```
+┌──────────────────────────────────────────────────────┐
+│               ACCOUNT RESEARCH                       │
+├──────────────────────────────────────────────────────┤
+│  LAYER 1 — WEB (always available)                    │
+│  ✓ Company overview, size, industry                  │
+│  ✓ Recent news, funding, leadership changes          │
+│  ✓ Hiring signals and open roles                     │
+│  ✓ Key people from LinkedIn                          │
+│  ✓ Product/service and customer base                 │
+├──────────────────────────────────────────────────────┤
+│  LAYER 2 — DEVREV (when account exists in DevRev)    │
+│  + Opportunities: stage, ACV, TCV, forecast          │
+│  + Tickets: open issues, severity, themes            │
+│  + Engagement: meetings, emails, discussions          │
+│  + Account metadata: tier, owner, contacts, ARR      │
+├──────────────────────────────────────────────────────┤
+│  LAYER 3 — ENRICHMENT (when tools connected)         │
+│  + Verified emails, phone numbers, org chart         │
+│  + Tech stack, funding history, investors             │
+│  + Intent signals, hiring velocity                    │
+└──────────────────────────────────────────────────────┘
+```
+
+---
+
+## Step 1: Parse the Request
+
+Determine what the user needs and which layers to activate.
+
+| Input | Type | Layers |
+|-------|------|--------|
+| "Research Stripe" | Company research | Web + DevRev (if exists) |
+| "Look up John Smith at Acme" | Person + company | Web + DevRev |
+| "Intel on acme.com" | Domain-based | Web + DevRev |
+| "Who is the CTO at Notion" | Role-based search | Web |
+| "Research Stripe — check DevRev too" | Explicit DevRev | Web + DevRev |
+| "Tell me about ACC-42" | DevRev account ID | DevRev + Web |
+
+**Default behavior**: Always run web search. Check DevRev if the user mentions DevRev data, provides a DevRev ID, or asks about internal relationship/pipeline/tickets.
+
+---
+
+## Step 2: Web Search (Always)
+
+Run these searches in parallel:
+
+1. `"[Company name]"` — Homepage, about page
+2. `"[Company name] news"` — Recent announcements (last 90 days)
+3. `"[Company name] funding"` — Investment history
+4. `"[Company name] careers"` — Hiring signals
+5. `"[Person name] [Company] LinkedIn"` — Profile info (if person research)
+6. `"[Company name] product"` — What they sell
+7. `"[Company name] customers"` — Who they serve
+
+**Extract**: company description, positioning, recent news, leadership team, open roles, technology mentions, customer base.
+
+---
+
+## Step 3: DevRev Data (When Applicable)
+
+Activate when: user asks for internal data, provides a DevRev ID, or says "check DevRev", "our data", "what do we have on them", "pipeline", "tickets", "relationship history".
+
+### Tools
+
+1. **HybridSearch** — Find account by name, get DON ID.
+2. **FetchObjectContext** — Full object details by DON or display ID.
+3. **GetKGSchema** — Full knowledge graph schema. Call before any SQL path.
+4. **GetNodeSchema** — Schema details for a specific node.
+5. **NLToSQL** — Convert natural language to SQL. Never write SQL yourself.
+6. **ExecuteSQL** — Run SQL from NLToSQL. Always add LIMIT 500.
+7. **MeetingSummaryOpp** — Meeting summaries linked to an opportunity.
+8. **EmailSummaryOpp** — Email summaries linked to an opportunity.
+9. **OpportunityDiscussions** — Discussion threads linked to an opportunity.
+10. **WebSearch** — External web intelligence.
+
+### DevRev Data Gathering Sequence
+
+1. **HybridSearch** to find account by name → get DON ID
+2. **FetchObjectContext** on account DON → owner, tier, industry, contacts, ARR
+3. **SQL path** (GetKGSchema → GetNodeSchema → NLToSQL → ExecuteSQL) for:
+   - Linked opportunities: display ID, title, stage, ACV, TCV, owner, close date, forecast category
+   - Linked tickets: display ID, title, severity, stage, created date
+   - LIMIT 500. Exclude duplicates silently.
+4. **FetchObjectContext** on top opportunities (stage 3+) for deeper context
+5. **MeetingSummaryOpp** + **EmailSummaryOpp** on active opportunities for engagement history
+6. **OpportunityDiscussions** for internal notes and themes
+
+### Account Disambiguation
+
+Multiple accounts can share the same name. If one match found — state assumption and proceed. If multiple — list them and ask user to select.
+
+---
+
+## Step 4: Enrichment (When Tools Connected)
+
+If enrichment tools are available:
+1. Enrich company → firmographics, funding, tech stack
+2. Search people → org chart, contact list
+3. Enrich person → verified email, phone, background
+4. Get signals → intent data, hiring velocity
+
+---
+
+## Step 5: Synthesize
+
+1. Combine all layers — prioritize enrichment > DevRev > web for accuracy
+2. Identify qualification signals (positive, concerns, unknowns)
+3. Generate talking points tailored to the person/account
+4. Recommend approach and next steps
+5. Be explicit about what data came from which source
+
+---
+
+## Output Format
+
+Only include sections where actual data exists. Omit sections entirely rather than guessing.
+
+### Full Overview (Company Research)
+
+```markdown
+# Research: [Company Name]
+
+**Generated:** [Date]
+**Sources:** Web Search [+ DevRev] [+ Enrichment]
+
+---
+
+## Quick Take
+
+[2-3 sentences: who they are, why they might need you, best angle for outreach]
+
+---
+
+## Company Profile
+
+| Field | Value |
+|-------|-------|
+| **Company** | [Name] |
+| **Website** | [URL] |
+| **Industry** | [Industry] |
+| **Size** | [Employee count] |
+| **Headquarters** | [Location] |
+| **Founded** | [Year] |
+| **Funding** | [Stage + amount if known] |
+| **Revenue** | [Estimate if available] |
+
+### What They Do
+[1-2 sentence description of business, product, customers]
+
+### Recent News
+- **[Headline]** — [Date] — [Why it matters for outreach]
+- **[Headline]** — [Date] — [Why it matters]
+
+### Hiring Signals
+- [X] open roles in [Department]
+- Notable: [Relevant roles — Engineering, Sales, AI/ML]
+- Growth indicator: [Interpretation]
+
+---
+
+## Key People
+
+### [Name] — [Title]
+| Field | Detail |
+|-------|--------|
+| **LinkedIn** | [URL] |
+| **Background** | [Prior companies, education] |
+| **Tenure** | [Time at company] |
+| **Email** | [If enrichment available] |
+
+**Talking Points:**
+- [Personal hook based on background]
+- [Professional hook based on role]
+
+---
+
+## DevRev Relationship [If DevRev data available]
+
+| Field | Detail |
+|-------|--------|
+| **Account Tier** | [Tier] |
+| **Account Owner** | [Name] |
+| **ARR** | [Value] |
+| **Status** | [New / Prospect / Customer / Churned] |
+| **Last Engagement** | [Date and type] |
+
+### Pipeline
+
+| Opp ID | Title | Stage | ACV | TCV | Owner | Close Date |
+|--------|-------|-------|-----|-----|-------|------------|
+| [ID] | [Title] | [Stage] | [ACV] | [TCV] | [Owner] | [Date] |
+
+**Pipeline Summary:** [X] active opps, $[Y] total ACV, [Z] closed won
+
+### Open Tickets
+
+| Ticket | Title | Severity | Stage | Created |
+|--------|-------|----------|-------|---------|
+| [ID] | [Title] | [Severity] | [Stage] | [Date] |
+
+### Engagement History
+- [Date] — [Meeting/Email] — [Key points]
+- [Date] — [Meeting/Email] — [Key points]
+
+### Internal Themes
+[Recurring topics from discussions, tickets, and internal notes]
+
+---
+
+## Tech Stack [If Enrichment Available]
+
+| Category | Tools |
+|----------|-------|
+| **Cloud** | [AWS, GCP, Azure] |
+| **Data** | [Snowflake, Databricks] |
+| **CRM** | [Salesforce, HubSpot] |
+| **Other** | [Relevant tools] |
+
+**Integration Opportunity:** [How your product fits their stack]
+
+---
+
+## Qualification Signals
+
+### Positive
+- ✅ [Signal and evidence]
+
+### Concerns
+- ⚠️ [Concern and what to watch]
+
+### Unknown (Ask in Discovery)
+- ❓ [Gap in understanding]
+
+---
+
+## Recommended Approach
+
+**Best Entry Point:** [Person and why]
+
+**Opening Hook:** [What to lead with based on research]
+
+**Discovery Questions:**
+1. [Question about their situation]
+2. [Question about pain points]
+3. [Question about decision process]
+
+**Recommended Next Steps:**
+1. [Action with owner and timeline]
+2. [Action with owner and timeline]
+
+---
+
+## Sources
+- [Source 1](URL)
+- [DevRev objects referenced: DON IDs]
+```
+
+### Person Research
+
+Focus on: background, role, LinkedIn activity, talking points, DevRev contact history if available.
+
+### Targeted Question
+
+For simple questions ("Who owns the Stripe account?", "What's their ARR?") — return a 1-3 sentence direct answer. No full brief needed.
+
+---
+
+## Signal Interpretation Guide
+
+### Product Signals (1st-Party)
+| Signal | Meaning |
+|--------|---------|
+| Active seats increasing | Expansion opportunity |
+| Feature adoption spike | Deepening engagement — good for expansion talk |
+| Login frequency drop | Churn risk — proactive outreach needed |
+| Trial started | Active evaluation — time-sensitive |
+| Trial nearing expiry | Decision point — immediate action |
+
+### Intent Signals (3rd-Party)
+| Signal | Meaning |
+|--------|---------|
+| Hiring for relevant roles | Growing team, budget exists |
+| Funding announced | New budget likely — congratulate and reach out |
+| Tech stack change | May need new integrations |
+| Competitive product removed | Window of opportunity — very high priority |
+
+### Relationship Signals
+| Signal | Meaning |
+|--------|---------|
+| Recent meeting logged | Active relationship |
+| No meeting in 90+ days | Relationship cooling — check in |
+| Open opportunity | Active deal — coordinate with AE |
+| Champion job change | Risk or new opportunity |
+
+**Principles:**
+1. Recency matters most — yesterday's signal outweighs last quarter's
+2. Signal clusters > single signals
+3. Absence of signals is a signal — minimal activity at a paid account = risk
+4. Contextualize against account stage — trial: conversion signals, mature: expansion/churn
+
+---
+
+## Quality Standards
+
+- Every fact must trace to a data source — never speculate
+- Be explicit when data is missing or stale
+- Prioritize enrichment data > DevRev data > web data for accuracy
+- Keep full briefings readable in 2-3 minutes
+- Show the SQL query used at the bottom when DevRev data is queried

package/skills/account-research/references/signals-guide.md

@@ -0,0 +1,52 @@
+# Common Room Signal Types — Interpretation Guide
+
+## Signal Categories
+
+### Product Signals (1st-Party)
+
+| Signal | What it means |
+|--------|--------------|
+| Active seats increasing | Expansion within the account — outreach opportunity |
+| Feature adoption (new features used) | Product engagement deepening — good for expansion talk |
+| Login frequency spike | Increased engagement — follow up to understand why |
+| Login frequency drop | Risk of disengagement or churn — proactive outreach needed |
+| Trial started | Active evaluation — time-sensitive, prioritize |
+| Trial nearing expiry | Decision point approaching — immediate action |
+| Support tickets opened | Potential friction — check for patterns |
+
+### Community Signals (2nd-Party)
+
+| Signal | What it means |
+|--------|--------------|
+| New community post | Actively engaged, has a question or idea |
+| Reply / reaction to post | Community participation |
+| Forum thread started | Seeking help or sharing feedback — can engage directly |
+| Documentation viewed (specific page) | Researching a specific feature — high value if tied to expansion area |
+| Event registration/attendance | Strong engagement and intent signal |
+
+### Intent Signals (3rd-Party)
+
+| Signal | What it means |
+|--------|--------------|
+| Hiring for relevant roles | Growing team, budget exists |
+| Funding announced | New budget likely available — reach out congratulating |
+| Company news / press mention | Good hook for outreach |
+| Tech stack change | May need new integrations |
+| Competitive product removed from stack | Window of opportunity — very high priority |
+| Website activity spike | Active research phase |
+
+### Relationship Signals
+
+| Signal | What it means |
+|--------|--------------|
+| Recent meeting logged | Active relationship — context available |
+| No meeting in 90+ days | Relationship cooling — check in |
+| Open opportunity in CRM | Active deal — coordinate with AE |
+| Champion job change | Relationship risk or opportunity |
+
+## Signal Interpretation Principles
+
+1. **Recency matters most.** A signal from yesterday far outweighs one from 6 months ago. Always note timestamps.
+2. **Signal clusters > single signals.** Multiple signals in the same direction are much stronger than any individual one.
+3. **Absence of signals is a signal.** Minimal usage + no community engagement at a paid account = risk indicator.
+4. **Contextualize against account stage.** Trial: conversion signals dominate. Mature customer: expansion and churn-risk. Prospect: intent signals are paramount.