geekbot-cli 0.1.0

package/skills/geekbot/reporter-workflows.md

@@ -0,0 +1,275 @@
+# Reporter Workflows
+
+Detailed guide for the AI-assisted reporting experience. The SKILL.md
+covers the 5-step pipeline at a high level; this document covers the
+full flow including tone calibration, blocker carry-over, and edge cases.
+
+## Table of Contents
+
+1. [Report Drafting Pipeline (detailed)](#report-drafting-pipeline)
+2. [Tone Calibration](#tone-calibration)
+3. [Blocker Carry-Over Logic](#blocker-carry-over-logic)
+4. [Edge Cases](#edge-cases)
+
+---
+
+## Report Drafting Pipeline
+
+### Step 1: Identify the standup
+
+Run `geekbot standup list` to get the user's standups.
+
+- **Single standup**: Use it automatically. Mention which one: "I see you're
+  in the 'Daily Standup' — let's draft your report for that."
+- **Multiple standups**: Present a short list (ID, name, channel) and ask
+  which one. If the user's request hints at one ("my daily"), match on name.
+- **No standups**: The user might not be a participant in any standup.
+  Suggest they check with their manager or run `geekbot standup list --admin`
+  if they're an admin.
+
+### Step 2: Fetch questions
+
+```bash
+geekbot standup get <standup_id>
+```
+
+Extract from the response:
+- `questions[].id` — you need these for the report submission
+- `questions[].text` — show these to the user and use as draft structure
+
+Store the question ID ↔ text mapping for use in step 5.
+
+### Step 3: Gather context
+
+Context comes from three sources. Check them in this order — each one makes
+the draft richer.
+
+#### Source A: Connected MCP servers (opportunistic enrichment)
+
+Check what MCP servers are available in the current session. Use whatever
+is connected to pull the user's recent activity. This is what transforms
+"help me write my standup" from a Q&A session into a one-click draft.
+
+The key concept: map MCP entities to standup questions — what they *did*,
+what they *will do*, and what's *blocking* them.
+
+| Source | Entity | Maps to |
+|--------|--------|---------|
+| GitHub/GitLab | Merged PRs, closed issues, review comments | "What did you do?" |
+| GitHub/GitLab | Open/draft PRs (authored) | "What will you do?" |
+| GitHub/GitLab | PRs with changes requested | "Blockers?" |
+| Jira/Linear/Asana | Tickets moved to Done | "What did you do?" |
+| Jira/Linear/Asana | In Progress tickets | "What will you do?" |
+| Jira/Linear/Asana | Blocked/On Hold tickets | "Blockers?" |
+| Calendar | Meetings attended since last report | "What did you do?" |
+| Calendar | Upcoming meetings today | "What will you do?" |
+| Slack | Threads participated in, announcements | Any question |
+
+Filter calendar noise: skip the standup itself, recurring 1:1s, and
+all-day events unless meaningful (offsites, deadlines).
+
+**Deduplication:** Group related entities across tools — "Merged PR #342,
+closes PROJ-89" is better than listing each separately.
+
+**Identity matching:** MCP servers use different identifiers (Slack IDs,
+GitHub usernames, emails). If they don't match, ask the user once and
+reuse for the conversation.
+
+**Enrichment flow:**
+1. Silently check which MCP servers are connected
+2. Pull recent activity from each (since last report date)
+3. Deduplicate across tools, group by standup question
+4. Present: "I pulled your recent activity — here's what I found"
+
+If no MCP servers are connected, skip silently. Don't mention missing
+access unprompted — explain only if the user asks why the draft isn't
+auto-populated.
+
+#### Source B: Previous Geekbot reports (always available)
+
+```bash
+geekbot report list --standup-id <id> --user-id <uid> --limit 5
+```
+
+Where `<uid>` comes from `geekbot me show` → `data.id`. Extract: typical
+answer length, writing style (bullets vs prose), recurring themes, and
+any unresolved blockers for carry-over.
+
+#### Source C: The user's direct input
+
+**With MCP context:** Show what you found, ask "Anything to add, correct,
+or remove?" — the user validates instead of recalling from scratch.
+
+**Without MCP:** This is the primary source. Let the user dump context
+freely ("What have you been working on?") — you structure it into answers.
+
+#### Combining sources
+
+Merge priority: user corrections > MCP specifics (PR numbers, ticket IDs) >
+previous reports (style/tone) > user narrative input (the "why").
+
+### Step 4: Draft answers
+
+For each question in the standup, draft an answer that:
+
+1. **Addresses the question directly** — don't go off-topic
+2. **Matches the user's historical style** (see Tone Calibration below)
+3. **Leads with specifics from MCP data** — PR numbers, ticket IDs,
+   meeting names add credibility and save the user from remembering details
+4. **Incorporates their direct input** — the user's words provide narrative
+   and context that tools can't capture
+5. **Includes blocker carry-over** — surface unresolved blockers from
+   previous reports (see Blocker Carry-Over below)
+
+**Example with enrichment:**
+```
+Q: What have you done since yesterday?
+A: Merged PR #342 (auth module refactor), closed PROJ-89 (payment webhook
+   bug). Had a sync with the API team about token rotation strategy.
+
+Q: What will you do today?
+A: Starting on the new billing API (PROJ-102). PR #345 is waiting for
+   review from @alice.
+
+Q: Any blockers?
+A: Still waiting on the staging deploy from DevOps (carrying over from
+   Tuesday). Also blocked on PROJ-98 — needs design sign-off.
+```
+
+vs. **without enrichment (user input only):**
+```
+Q: What have you done since yesterday?
+A: Fixed the payment webhook bug and worked on the auth refactor.
+```
+
+The enriched version is more useful for the team reading the report.
+
+If the user didn't provide enough context for a specific question, ask
+about that question specifically rather than inventing content.
+
+### Step 5: Review and post
+
+Present the complete draft clearly:
+
+```
+Here's your draft for "Daily Standup":
+
+Q: What did you work on yesterday?
+A: Finished the auth module refactor and opened PR #342 for review.
+
+Q: What are you working on today?
+A: Starting integration tests for the new auth flow. Meeting with
+   the API team at 14:00 to discuss token rotation.
+
+Q: Any blockers?
+A: Still waiting on the staging environment deploy from DevOps
+   (carried over from Tuesday).
+
+Ready to submit?
+```
+
+On explicit approval, build and execute:
+
+```bash
+geekbot report create \
+  --standup-id 123 \
+  --answers '{"101":"Finished the auth module refactor and opened PR #342 for review.","102":"Starting integration tests for the new auth flow. Meeting with the API team at 14:00 to discuss token rotation.","103":"Still waiting on the staging environment deploy from DevOps (carried over from Tuesday)."}'
+```
+
+Confirm success with the report ID and a brief summary.
+
+---
+
+## Tone Calibration
+
+Match the user's existing reporting style. This matters — people notice
+when their standup answers suddenly sound different.
+
+### What to analyse from historical reports
+
+| Signal | How to detect | How to match |
+|--------|--------------|--------------|
+| **Length** | Average character count per answer | Keep within ±20% of their norm |
+| **Structure** | Bullets vs prose vs numbered lists | Mirror the format |
+| **Formality** | "Completed authentication module" vs "wrapped up auth stuff" | Match register |
+| **Detail level** | PR numbers, ticket refs vs high-level summaries | Include same specificity |
+| **Emoji / voice** | Present or absent; "I did X" vs "Did X" vs "Completed X" | Mirror exactly |
+
+**If terse bullet points historically** → draft terse bullets, don't expand.
+**If narrative with context** → draft with similar detail and flow.
+**First-time reporter** → default to concise prose, 1–3 sentences per question.
+
+---
+
+## Blocker Carry-Over Logic
+
+One of the most valuable parts of AI-assisted reporting: automatically
+surfacing unresolved blockers so they don't silently disappear.
+
+### Detection
+
+Scan last 3–5 reports for blocker-related questions (keywords: "block",
+"stuck", "impediment", "waiting", "depend"). Classify answers as **no
+blocker** ("None", "All clear", "N/A", short negatives) or **has blocker**
+(anything else).
+
+### Resolution detection
+
+- Later report's blocker answer is "None" or similar → resolved
+- Later report mentions same topic in progress answer → resolved
+- Same blocker in most recent report → still active
+
+### Carry-over presentation
+
+Surface active blockers during step 4: *"In your last report (Tuesday),
+you mentioned waiting on the staging deploy. Is that still blocking you?"*
+
+- **Still blocked** → include, note it's a carry-over
+- **Resolved** → omit (optionally mention resolution in progress answer)
+- **Changed** → update the description
+
+### Don't over-carry
+
+Only carry over from last 3–5 reports. If a blocker persists 2+ weeks,
+still surface but don't belabour it. If the user says "no blockers" after
+you surface a carry-over, respect that.
+
+---
+
+## Edge Cases
+
+### User in multiple standups with overlapping questions
+
+If multiple standups have similar questions (common with "blockers" across
+a daily standup and a weekly sync), draft each report independently. A
+blocker reported in one standup should be surfaced for the other if it's
+the same blocker — but the framing may differ (daily: tactical, weekly:
+strategic).
+
+### Standup with many questions (>5)
+
+Some standups (e.g., Sales Report, Well-being Check-in) have 5+ questions.
+Don't try to gather context for all at once. Process in batches:
+1. Draft the first 3 answers based on initial context
+2. Ask about the remaining questions specifically
+3. Complete the draft
+
+### User provides minimal input
+
+If the user says something like "nothing much today" or "same as yesterday":
+- For progress questions: pull from the last report and frame as continuation
+  ("Still working on the auth refactor from yesterday?")
+- For blocker questions: check carry-over, default to "No blockers" if clear
+- Don't pad — if they want a short report, draft a short report
+
+### Report already submitted
+
+If the user tries to submit a report and the CLI returns a conflict (exit
+code 8), they may have already reported today. Inform them and ask if they
+want to view their existing report instead.
+
+### Standup is inactive or paused
+
+If `geekbot standup get` shows the standup isn't currently active, let the
+user know. They can still submit a report manually, but the standup won't
+trigger automatically until reactivated.

package/skills/geekbot/standup-templates.json

@@ -0,0 +1,244 @@
+{
+	"standup_templates": [
+		{
+			"id": "daily-standup",
+			"name": "Daily Standup",
+			"description": "Track daily updates and blockers on autopilot. The classic async standup for engineering and general teams.",
+			"categories": ["daily-syncs", "team-updates", "remote-collaboration"],
+			"roles": ["team-leads", "project-managers", "product-managers", "agile-team-members"],
+			"questions": [
+				{ "text": "What have you done since yesterday?" },
+				{ "text": "What will you do today?" },
+				{ "text": "Anything blocking your progress?" },
+				{ "text": "How do you feel today?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "10:00"
+			}
+		},
+		{
+			"id": "retrospective",
+			"name": "Retrospective",
+			"description": "Reflect on what went well and what could go better. Designed for sprint or project retrospectives.",
+			"categories": ["continuous-improvement", "remote-collaboration"],
+			"roles": ["agile-team-members", "product-managers", "team-leads"],
+			"questions": [
+				{ "text": "What went well?" },
+				{ "text": "What didn't go so well?" },
+				{ "text": "What have you learned?" },
+				{ "text": "What still puzzles you?" }
+			],
+			"defaults": {
+				"days": "Fri",
+				"time": "16:30",
+				"note": "Typically bi-weekly, aligned with sprint cadence"
+			}
+		},
+		{
+			"id": "sales-report",
+			"name": "Sales Report",
+			"description": "Report sales progress and track team performance. End-of-day sales metrics and pipeline updates.",
+			"categories": ["daily-syncs", "team-updates"],
+			"roles": ["team-leads"],
+			"questions": [
+				{ "text": "How many meetings did you setup today?" },
+				{ "text": "How many client conversations did you have today?" },
+				{ "text": "How many new leads did you create today?" },
+				{ "text": "Anything you'd like to add?" },
+				{ "text": "Anything blocking your progress?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "16:30"
+			}
+		},
+		{
+			"id": "quick-check-in",
+			"name": "Quick Check-in",
+			"description": "Keep everyone in the loop with 3 quick questions. Lighter than a full standup, good for small teams.",
+			"categories": ["daily-syncs", "team-updates", "remote-collaboration"],
+			"roles": ["team-leads", "project-managers"],
+			"questions": [
+				{ "text": "What's your main focus today?" },
+				{ "text": "How are you feeling?" },
+				{ "text": "Anything blocking your progress?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "09:00"
+			}
+		},
+		{
+			"id": "well-being-check-in",
+			"name": "Well-being Check-in",
+			"description": "Check in on how your team is really doing. Covers productivity, stress, and satisfaction. Best run anonymously.",
+			"categories": ["team-well-being", "remote-collaboration"],
+			"roles": ["people-managers"],
+			"questions": [
+				{ "text": "Thinking about this past week: how productive do you feel you were?" },
+				{ "text": "Do you feel you've had more wins or roadblocks this past week?" },
+				{ "text": "How stressful did you find work in general this week?" },
+				{ "text": "How satisfied do you feel about the work you've completed this week?" },
+				{ "text": "Do you feel satisfied with your work-life balance?" },
+				{ "text": "Overall, how do you feel about your level of work-related stress?" },
+				{ "text": "Do you feel you can discuss concerns with your manager as often as needed?" }
+			],
+			"defaults": {
+				"days": "Fri",
+				"time": "16:00",
+				"note": "Typically bi-weekly, anonymous"
+			}
+		},
+		{
+			"id": "confidential-check-in",
+			"name": "Confidential Check-in",
+			"description": "Run multiple 1-on-1s with your team all in one go. Replies stay private between manager and each participant.",
+			"categories": ["team-updates", "remote-collaboration"],
+			"roles": ["project-managers", "team-leads"],
+			"questions": [
+				{ "text": "Was anything a particular struggle?" },
+				{ "text": "If there was one thing I could do to help you, what would it be?" },
+				{ "text": "On a scale of 1-10, how happy are you with your work-life balance?" },
+				{ "text": "Growth-wise, where do you want to focus next month?" },
+				{ "text": "Anything you'd like to add?" }
+			],
+			"defaults": {
+				"days": "Fri",
+				"time": "15:00",
+				"note": "Weekly or bi-weekly, private channel between manager and participant"
+			}
+		},
+		{
+			"id": "meeting-notes",
+			"name": "Meeting Notes",
+			"description": "Sum up the talking points of every meeting. Structured capture of decisions and action items.",
+			"categories": ["team-updates"],
+			"roles": ["project-managers", "product-managers"],
+			"questions": [
+				{ "text": "What were the main talking points?" },
+				{ "text": "What decisions were made?" },
+				{ "text": "What are the action items and who owns them?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "17:00",
+				"note": "Trigger on-demand after meetings rather than on a fixed schedule"
+			}
+		},
+		{
+			"id": "today-i-learned",
+			"name": "Today I Learned",
+			"description": "Inspire your team to learn something new. A lightweight knowledge-sharing ritual.",
+			"categories": ["continuous-improvement", "team-bonding"],
+			"roles": ["team-leads"],
+			"questions": [
+				{ "text": "What did you learn today?" },
+				{ "text": "How might this be useful for the team?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "17:00"
+			}
+		},
+		{
+			"id": "product-changelog",
+			"name": "Product Changelog",
+			"description": "Keep track of changes in product development. Structured release and change tracking.",
+			"categories": ["team-updates", "continuous-improvement"],
+			"roles": ["product-managers"],
+			"questions": [
+				{ "text": "What changed or shipped today?" },
+				{ "text": "What's the user impact?" },
+				{ "text": "Any follow-up items or known issues?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "17:00"
+			}
+		},
+		{
+			"id": "incident-log",
+			"name": "Incident Log",
+			"description": "Log incidents to share with the team. Structured incident reporting and post-mortem capture.",
+			"categories": ["team-updates"],
+			"roles": ["team-leads"],
+			"questions": [
+				{ "text": "What happened?" },
+				{ "text": "What was the impact?" },
+				{ "text": "What was the root cause?" },
+				{ "text": "What are the follow-up actions?" }
+			],
+			"defaults": {
+				"days": "Mon,Tue,Wed,Thu,Fri",
+				"time": "09:00",
+				"note": "Trigger on-demand when incidents occur"
+			}
+		},
+		{
+			"id": "monday-watercooler",
+			"name": "Monday Water Cooler",
+			"description": "Spark Monday morning chitchat with a friendly question. Team bonding for remote teams.",
+			"categories": ["team-bonding"],
+			"roles": ["team-leads", "people-managers"],
+			"questions": [
+				{ "text": "What was the highlight of your weekend?" },
+				{ "text": "What are you looking forward to this week?" }
+			],
+			"defaults": {
+				"days": "Mon",
+				"time": "09:30"
+			}
+		},
+		{
+			"id": "team-feedback",
+			"name": "Team Feedback",
+			"description": "Let your teammates know how they're doing. Structured peer feedback collection.",
+			"categories": ["continuous-improvement", "team-bonding"],
+			"roles": ["team-leads", "people-managers"],
+			"questions": [
+				{ "text": "Who on the team did great work recently and what did they do?" },
+				{ "text": "What's one thing we could do better as a team?" },
+				{ "text": "Any shout-outs or kudos?" }
+			],
+			"defaults": {
+				"days": "Fri",
+				"time": "16:00"
+			}
+		}
+	],
+	"poll_templates": [
+		{
+			"id": "yes-no",
+			"name": "Yes / No",
+			"description": "Make fast decisions with simple Yes/No votes.",
+			"question": "Do you agree with the proposal?",
+			"choices": ["Yes", "No"],
+			"note": "Replace the question with your actual decision topic"
+		},
+		{
+			"id": "agree-disagree",
+			"name": "Agree / Disagree",
+			"description": "Quickly gauge sentiment on a topic with a Likert-style scale.",
+			"question": "How do you feel about this proposal?",
+			"choices": ["Strongly Agree", "Agree", "Neutral", "Disagree", "Strongly Disagree"],
+			"note": "Replace the question with your actual topic"
+		},
+		{
+			"id": "employee-nps",
+			"name": "Employee NPS Survey",
+			"description": "Evaluate and track employee commitment and loyalty with a standard NPS question.",
+			"question": "On a scale of 0-10, how likely are you to recommend this company as a place to work?",
+			"choices": ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10"],
+			"note": "NPS = % Promoters (9-10) minus % Detractors (0-6)"
+		},
+		{
+			"id": "team-feedback-weekly",
+			"name": "Team Feedback Weekly",
+			"description": "Gather weekly insights on team performance and morale.",
+			"question": "How would you rate this week's team performance?",
+			"choices": ["Excellent", "Good", "Average", "Below Average", "Poor"],
+			"note": "Good for tracking team health trends over time"
+		}
+	]
+}

package/src/auth/keychain.ts

@@ -0,0 +1,38 @@
+import { Entry } from "@napi-rs/keyring";
+
+const SERVICE = "geekbot-cli";
+const ACCOUNT = "api-key";
+
+/**
+ * Retrieve API key from OS keychain.
+ * Returns null if keychain is unavailable or no entry exists.
+ */
+export function getKeychainKey(): string | null {
+	try {
+		const entry = new Entry(SERVICE, ACCOUNT);
+		return entry.getPassword();
+	} catch {
+		return null;
+	}
+}
+
+/**
+ * Store API key in OS keychain.
+ * Throws if keychain is unavailable (caller should catch and suggest env var).
+ */
+export function setKeychainKey(apiKey: string): void {
+	if (!apiKey.trim()) {
+		throw new Error("API key must not be empty");
+	}
+	const entry = new Entry(SERVICE, ACCOUNT);
+	entry.setPassword(apiKey);
+}
+
+/**
+ * Delete API key from OS keychain.
+ * Throws if keychain is unavailable or no entry exists.
+ */
+export function deleteKeychainKey(): void {
+	const entry = new Entry(SERVICE, ACCOUNT);
+	entry.deletePassword();
+}

package/src/auth/resolver.ts

@@ -0,0 +1,44 @@
+import { CliError } from "../errors/cli-error.ts";
+import { ExitCode } from "../errors/exit-codes.ts";
+import { getKeychainKey as _getKeychainKey } from "./keychain.ts";
+
+export interface CredentialResult {
+	apiKey: string;
+	source: "flag" | "env" | "keychain";
+}
+
+export async function resolveCredential(
+	options: { apiKeyFlag?: string },
+	getKeychainKeyImpl?: typeof _getKeychainKey,
+): Promise<CredentialResult> {
+	// Priority 1: --api-key flag
+	if (options.apiKeyFlag) {
+		return { apiKey: options.apiKeyFlag.trim(), source: "flag" };
+	}
+
+	// Priority 2: GEEKBOT_API_KEY env var
+	const envKey = process.env.GEEKBOT_API_KEY;
+	if (envKey) {
+		return { apiKey: envKey.trim(), source: "env" };
+	}
+
+	// Priority 3: OS keychain
+	const getKey = getKeychainKeyImpl ?? _getKeychainKey;
+	try {
+		const keychainKey = getKey();
+		if (keychainKey) {
+			return { apiKey: keychainKey.trim(), source: "keychain" };
+		}
+	} catch {
+		// Keychain unavailable (headless, CI) -- fall through to error
+	}
+
+	// No credential found -- list all sources checked
+	throw new CliError(
+		"No API key found. Checked: --api-key flag, GEEKBOT_API_KEY environment variable, OS keychain.",
+		"auth_missing",
+		ExitCode.AUTH,
+		false,
+		"Set GEEKBOT_API_KEY environment variable or run: geekbot auth setup",
+	);
+}

package/src/cli/commands/auth.ts

@@ -0,0 +1,56 @@
+import { Command } from "commander";
+import { handleError } from "../../errors/error-handler.ts";
+import {
+	handleAuthRemove,
+	handleAuthSetup,
+	handleAuthStatus,
+} from "../../handlers/auth-handlers.ts";
+import { getGlobalOptions } from "../globals.ts";
+
+export function createAuthCommand(): Command {
+	const auth = new Command("auth").description("Manage authentication");
+
+	auth
+		.command("setup")
+		.description("Interactively configure and store API key")
+		.addHelpText(
+			"after",
+			"\nExamples:\n  geekbot auth setup\n  geekbot --api-key YOUR_KEY auth setup",
+		)
+		.action(async function (this: Command) {
+			const globalOpts = getGlobalOptions(this);
+			try {
+				await handleAuthSetup({ apiKey: globalOpts.apiKey }, globalOpts);
+			} catch (error) {
+				handleError(error, globalOpts.debug);
+			}
+		});
+
+	auth
+		.command("status")
+		.description("Verify stored credentials work")
+		.addHelpText("after", "\nExamples:\n  geekbot auth status")
+		.action(async function (this: Command) {
+			const globalOpts = getGlobalOptions(this);
+			try {
+				await handleAuthStatus(globalOpts);
+			} catch (error) {
+				handleError(error, globalOpts.debug);
+			}
+		});
+
+	auth
+		.command("remove")
+		.description("Remove stored API key from OS keychain")
+		.addHelpText("after", "\nExamples:\n  geekbot auth remove")
+		.action(async function (this: Command) {
+			const globalOpts = getGlobalOptions(this);
+			try {
+				await handleAuthRemove(globalOpts);
+			} catch (error) {
+				handleError(error, globalOpts.debug);
+			}
+		});
+
+	return auth;
+}

package/src/cli/commands/me.ts

@@ -0,0 +1,34 @@
+import { Command } from "commander";
+import { handleError } from "../../errors/error-handler.ts";
+import { handleMeShow, handleMeTeams } from "../../handlers/me-handlers.ts";
+import { getGlobalOptions } from "../globals.ts";
+
+export function createMeCommand(): Command {
+	const me = new Command("me").description("View your profile and teams");
+
+	me.command("show")
+		.description("Show your Geekbot profile")
+		.addHelpText("after", "\nExamples:\n  geekbot me show")
+		.action(async function (this: Command) {
+			const globalOpts = getGlobalOptions(this);
+			try {
+				await handleMeShow(globalOpts);
+			} catch (error) {
+				handleError(error, globalOpts.debug);
+			}
+		});
+
+	me.command("teams")
+		.description("List teams you belong to")
+		.addHelpText("after", "\nExamples:\n  geekbot me teams")
+		.action(async function (this: Command) {
+			const globalOpts = getGlobalOptions(this);
+			try {
+				await handleMeTeams(globalOpts);
+			} catch (error) {
+				handleError(error, globalOpts.debug);
+			}
+		});
+
+	return me;
+}