A follow-up dashboard built on accounts, opportunities and commitments from both sides: overdue and soon-due commitments, opportunities with overdue follow-up or expected to close within 30 days, at-risk accounts and renewals. Amounts are shown per currency without conversion; stage counts are the current distribution, not a funnel or repeat-purchase rate.
GeneralBusiness Ops
Business dashboardTeloaNeeds configurationApache-2.0v1.0.0
Extracts business rules from legacy code into Given/When/Then rule cards with file:line sources, plus a data-object catalog and questions for domain experts; comment-only "rules" are dropped and credentials masked. Derived from Anthropic's Claude Code plugin code-modernization: the Workflow-and-script sharding is removed, and its granularity, citation checks, P0 double check and duplicate merging are written into the skill; large scopes are sized first.
Unsent recap and tasks after a call. Own the after-call pack: a recap the owner can edit, the tasks each side owed, and dates pulled from the notes — then stop. Never send the recap to the customer or book the next meeting. Recap and tasks, still in the building. Sending is a later named L2.
Prepares one local Git commit: picks the files of the change, checks for credentials, drafts a message in the repository's style and shows you the list and commands; git add and git commit run only after you confirm. Derived from /commit in Anthropic's Claude Code plugin commit-commands: explicit paths only, a credential check first, no push, amend or hook bypass, and unattended AI colleague tasks hand over the proposal.
Material-change competitor watch. Own a standing watch on a named set of three to eight competitors. Snapshot public pages and surface only material changes — price, packaging, positioning, named-role hiring — with URLs and dates. Stay quiet when nothing material moved. Alert only when the page actually changed. Silence is a result.
Draft-only social and email variants. Own turning one approved source draft into review-ready variants for social, email, and short-form pages. Every variant stays labeled DRAFT. None go live, none get scheduled, none get published. One draft in. A set of variants out. Nothing ships.
A content dashboard following ideas through production, approval and publication: items awaiting approval or revision, overdue drafts, the next 7 days of schedule and the last 30 days of output. Impressions and conversions are totalled only from records with a stated source; unrecorded values show as missing, never as 0.
Marketing · New MediaMarketingBusiness OpsContent & Design
Business dashboardTeloaNeeds configurationApache-2.0v1.0.0
Clustered product asks, not a roadmap. Own clustering the same product request that is living in many Slack threads into one table with quotes, frequency, and a suggested issue — never a roadmap decision. Quotes and counts. You do not ship the roadmap.
Software Development · ProductSoftware DevelopmentData & ResearchBusiness Ops
A seven-phase feature workflow: understand the code, ask clarifying questions, compare approaches, implement only after you approve, then review. Derived from Anthropic's Claude Code plugin feature-dev: the three subagents become read-only role files, the review covers staged changes and new files, writes go through host confirmation, it never installs, commits or pushes on its own, and unattended AI colleague tasks are told to deliver only the plan.
Figma's official remote MCP service uses OAuth but only allows clients listed in the Figma MCP Catalog. Teloa is not on the list yet, so this connector cannot be added until approval.
Reviews security practices in Python, JavaScript/TypeScript and Go using language and framework references, with file-based findings and remediation guidance. Derived from the OpenAI Codex curated skill with documented changes (open-redirect validation tested with vectors in three languages, SRI, CSP, CSRF scope, override handling, react2shell and CVE-2026-23864 version facts, and others).
Go/no-go packet, never the publish. Own a dated launch as group lead: assign researcher, writer, and reviewer, track blockers, and stop at a go/no-go packet. Never publish. One owner per role. The human issues the ship verdict.
Software Development · ProductSoftware DevelopmentBusiness OpsCommunication & Collaboration
Assesses legacy code before modernization: size and complexity, technology, domain map, top technical debt, CWE-tagged security findings with masked credentials, documentation gaps and a recommended pattern; can rank several systems. Size indices rank systems, never a cost or timeline. Derived from Anthropic's Claude Code plugin code-modernization without its Workflow and report scripts or raw-secret option; code is analyzed read-only.
Linear official remote MCP service: list and filter issues, view issues, create or update them (save_issue), and list projects. Requires a Linear API key (Bearer token).
Three employees track competitor changes, adapt accepted content and assemble newsletters. The competitor analyst leads; channel variants and newsletters stay as drafts for review.
MarketingMarketing · New MediaContent & DesignData & Research
Guides building high-quality MCP servers in Python (FastMCP) or Node/TypeScript (MCP SDK), covering tool design, error handling, evaluation, and best practices; full reference docs included.
Pre-call brief from CRM, mail, and calendar. Own the pre-call brief for each named customer meeting. Reconstruct CRM, mail, calendar, and Slack so the owner walks in knowing who is in the room and the last promise on the thread. Never send a pre-read to the customer. Walk in knowing the last promise — the customer already lived the rest.
Read-only review of local Git changes or a named pull request, one pass per aspect (code quality, comments, tests, silent failures, type design), merged into a prioritized list with file:line. Derived from Anthropic's Claude Code plugin pr-review-toolkit: covers staged changes and new files, drops one project's hard-coded logging conventions, splits out code-editing simplification; never comments, approves or merges.
Unsent weekly newsletter from saved links. Own the weekly newsletter draft from saved links, notes, and mail the owner already collected. Return an unsent issue in house voice, with every item cited. Never send the issue or create a live Docs share beyond a draft. The issue is written. The send button stays with the owner.
MarketingMarketing · New MediaContent & DesignOffice & Docs
Notion's officially recommended remote MCP service for searching and reading pages and databases, creating and updating pages, querying data sources, and reading or writing comments. Authorized by Teloa via OAuth (dynamic client registration + PKCE) with automatic token refresh.
Account research and review-ready outreach. Own account research, contact prioritization, and review-ready outreach for a named account list. Stop at a review list. Never send or enroll. Volume without sounding like a sequence tool — and without sending.
Evidence-backed performance investigations. Own targeted performance investigations with evidence: dashboards, traces, and source links, facts separated from hypotheses, and no production changes. Hotspot, links, facts vs hypotheses — never touch production.
Software Development · ProductSoftware DevelopmentData & ResearchDev Tools
Three employees investigate performance, gather feature requests and coordinate releases. The performance investigator leads; requests become evidence-backed drafts and release decisions remain with you.
Software Development · ProductSoftware DevelopmentBusiness OpsData & Research
Three employees research accounts, prepare meetings and draft call follow-ups. The outbound researcher leads; outreach, recaps and proposed meeting times remain for your review.
Sentry official remote MCP: find organizations and projects, search issues and events, and read issue details by URL or ID. Authorized by Teloa via OAuth (dynamic client registration + PKCE) with automatic token refresh. Data transits sentry.io.
Slack's official remote MCP service for searching messages and channels and reading channel and user info (this connector requests read-only scopes and cannot send messages). Slack does not support dynamic client registration: create your own internal Slack app with PKCE enabled, enter its client_id (like 1234567890.1234567890) in the connection settings, then Teloa authorizes via OAuth (PKCE, no client secret).
A delivery dashboard built on requirements, blockers and release readiness: which requirements lack confirmed acceptance criteria, which are past their planned date, which blockers are open, and whether upcoming releases have their checklist and rollback plan ready. Delivery is judged by acceptance criteria, never by task counts.
Software Development · ProductSoftware DevelopmentBusiness Ops
Business dashboardTeloaNeeds configurationApache-2.0v1.0.0
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
Use for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into a skill\", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
Use when a developer wants to build or validate Block Kit layouts for Slack messages, modals, or Home tabs: message layouts, modals/forms/dialogs, Home tab interfaces, interactive buttons or menus, or modifying existing Block Kit JSON. Also trigger on any Slack UI component (sections, actions, inputs, headers, alerts, tables, carousels), the words "blocks" or "Block Kit Builder", a request to preview rendered blocks, or pasted JSON like "type": "section". Validates via the bl
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
Use when a developer wants to create, scaffold, or bootstrap a new Slack app or agent from scratch with the Slack CLI. Covers prerequisites, authentication, choosing a workspace to install into, and creating a project from a Bolt (JS or Python) template locally. Trigger on "create a Slack app", "new Bolt app", "start a Slack agent".
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use for /figure-it-out or 'figure it out'.
Sets a distinctive visual direction for new or reworked UI: settle palette, type and wireframe choices first and self-review them, check against common templated defaults, keep quality floors such as responsiveness, visible keyboard focus and reduced motion, and follow UI copy guidelines.
Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Creates a self-contained single-file HTML playground: controls on one side, a live preview on the other, and a copyable prompt at the bottom. Includes six templates: visual design, data queries, concept maps, document critique, diff review and code architecture.
Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.
Catch the user up on what changed in this chat since their last message, in a few plain sentences and small visuals. Give each action item just enough context to make the call. Use for /ketchup.
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".
Guides packaging a local MCP server together with its runtime into a single .mcpb file: writing the manifest.json file, Node or Python build pipelines, a local security checklist, and validate, pack and sign commands.
Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
Apply when you write, change, or keep a test. Call the code as its users do and assert the exact result they see. Rewrite or delete a test that would pass if every imported function returned undefined.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
Create Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow automations. Supports email, Slack, PagerDuty, Discord, and other notification actions.
Debug and fix a Sentry issue — find it (by link, ID, or search), pull full context (stack trace, breadcrumbs, trace, logs), optionally run Seer root-cause / autofix, apply the code fix, and resolve it via a `Fixes PROJECT-NAME-12A` commit/PR. Use when working a known error or hunting one down to fix.
Make Sentry stack traces readable — upload source maps for JavaScript/TypeScript, or debug files for native and mobile (dSYM, ProGuard/R8, NDK symbols, Dart obfuscation maps, .NET PDBs). Use when frames in Sentry show minified names, bundled paths, hex addresses, "unknown", or method names with no file/line, instead of your original source.
Guided entry point for using Sentry through your agent. Orients you to your current setup and, for a new project, sets up Sentry end to end with sane defaults — provision a project, install the SDK (errors, tracing, and whatever it enables by default), and confirm real telemetry reaches Sentry. Routes other intents (adding more signals, fixing issues) to the right skill.
Instrument an application with Sentry — detect the platform, install and initialize the SDK if needed, and wire up any signal — error monitoring, tracing/performance, logging, metrics, profiling, session replay, user feedback, cron check-ins, uptime monitors for the deployed app, and AI/LLM monitoring (agent runs, token cost, and conversations for OpenAI, Anthropic, Vercel AI, LangChain, Google GenAI, Pydantic AI, Laravel AI, Eve, Flue, the Cloudflare Agents SDK, and Workers
Configure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry, configuring collector pipelines for traces and logs, or routing telemetry from multiple services to Sentry projects.
Set up Sentry releases and deploy tracking — tag events with a version and environment, create the release in CI with its commits, and wire up suspect commits and code mappings, so Sentry can show which release introduced an issue, which commit is responsible, and release health. Use when asked to set up releases, track deploys, see what changed, or when issues show an unknown release or no suspect commit.
Full Sentry Snapshots setup for Apple/Cocoa projects. Use when asked to "setup SnapshotPreviews", "setup Apple snapshot testing", "upload Apple snapshots to Sentry", "setup Apple snapshot GitHub Actions", or "setup Apple selective snapshot testing".
Configure which models pstack uses per role and at what reasoning budget. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", "pstack budget", or changing pstack's model choices.
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
Use when a developer asks which Slack Web API method does something, needs a method's OAuth scopes or token type, wants to call or test a family.method endpoint (chat.postMessage, conversations.history, users.info, views.open), is handling cursor pagination (next_cursor) or rate limits (tier/ratelimited/Retry-After), or is debugging errors like missing_scope, invalid_auth, or channel_not_found. Also trigger on a pasted slack.com/api/ URL or docs.slack.dev/reference/methods li
Use when a developer works with the Slack CLI (slack command) to create, run, or manage a Slack app from the terminal: logging in or authenticating (slack login), adding a team or switching workspaces, running locally (slack run), deploying, editing the app manifest, calling Web API methods (slack api), or searching Slack docs (slack docs search).
Use when answering a conceptual or how-to question about Slack platform features, or when asked to look up, fetch, or summarize a docs.slack.dev page, including a pasted docs.slack.dev link. Covers finding and reading official Slack docs as clean markdown.
Use when writing, drafting, scheduling, or improving a Slack message, announcement, or reply sent via the Slack MCP tools (slack_send_message, slack_send_message_draft, slack_schedule_message). Covers Slack markdown formatting, message structure, thread etiquette, reactions, and scheduling, and points to the right dialect for canvases and Block Kit.
Use when locating messages, files, channels, or people across Slack, or gathering context before answering, with the search MCP tools (slack_search_public, slack_search_public_and_private, slack_search_channels, slack_search_users). Covers search modifiers (in:, from:, before:), file-type filters, natural-language vs. keyword search, and reading results in context.
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Use when a developer wants to test, try out, smoke-test, verify, or confirm that a Slack app built with the Slack CLI (or a plain Bolt app) actually works, by running it in a developer sandbox or a Free Team, never a workspace with real users, with `slack run` and exercising its real slash commands, shortcuts, events, actions, modals, App Home, and assistant surfaces. Also covers `slack doctor` and `slack manifest validate` health checks before hands-on testing.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence. Includes 51 of the original 53 skills; two with invalid native names are not installed.
Guides packaging a local MCP server together with its runtime into a single .mcpb file: writing the manifest.json file, Node or Python build pipelines, a local security checklist, and validate, pack and sign commands.
Prepares one local Git commit: picks the files of the change, checks for credentials, drafts a message in the repository's style and shows you the list and commands; git add and git commit run only after you confirm. Derived from /commit in Anthropic's Claude Code plugin commit-commands: explicit paths only, a credential check first, no push, amend or hook bypass, and unattended AI colleague tasks hand over the proposal.
A seven-phase feature workflow: understand the code, ask clarifying questions, compare approaches, implement only after you approve, then review. Derived from Anthropic's Claude Code plugin feature-dev: the three subagents become read-only role files, the review covers staged changes and new files, writes go through host confirmation, it never installs, commits or pushes on its own, and unattended AI colleague tasks are told to deliver only the plan.
Sets a distinctive visual direction for new or reworked UI: settle palette, type and wireframe choices first and self-review them, check against common templated defaults, keep quality floors such as responsiveness, visible keyboard focus and reduced motion, and follow UI copy guidelines.
Guides building high-quality MCP servers in Python (FastMCP) or Node/TypeScript (MCP SDK), covering tool design, error handling, evaluation, and best practices; full reference docs included.
Assesses legacy code before modernization: size and complexity, technology, domain map, top technical debt, CWE-tagged security findings with masked credentials, documentation gaps and a recommended pattern; can rank several systems. Size indices rank systems, never a cost or timeline. Derived from Anthropic's Claude Code plugin code-modernization without its Workflow and report scripts or raw-secret option; code is analyzed read-only.
Extracts business rules from legacy code into Given/When/Then rule cards with file:line sources, plus a data-object catalog and questions for domain experts; comment-only "rules" are dropped and credentials masked. Derived from Anthropic's Claude Code plugin code-modernization: the Workflow-and-script sharding is removed, and its granularity, citation checks, P0 double check and duplicate merging are written into the skill; large scopes are sized first.
Creates a self-contained single-file HTML playground: controls on one side, a live preview on the other, and a copyable prompt at the bottom. Includes six templates: visual design, data queries, concept maps, document critique, diff review and code architecture.
Read-only review of local Git changes or a named pull request, one pass per aspect (code quality, comments, tests, silent failures, type design), merged into a prioritized list with file:line. Derived from Anthropic's Claude Code plugin pr-review-toolkit: covers staged changes and new files, drops one project's hard-coded logging conventions, splits out code-editing simplification; never comments, approves or merges.
Reviews security practices in Python, JavaScript/TypeScript and Go using language and framework references, with file-based findings and remediation guidance. Derived from the OpenAI Codex curated skill with documented changes (open-redirect validation tested with vectors in three languages, SRI, CSP, CSRF scope, override handling, react2shell and CVE-2026-23864 version facts, and others).
Figma's official remote MCP service uses OAuth but only allows clients listed in the Figma MCP Catalog. Teloa is not on the list yet, so this connector cannot be added until approval.
Linear official remote MCP service: list and filter issues, view issues, create or update them (save_issue), and list projects. Requires a Linear API key (Bearer token).
Notion's officially recommended remote MCP service for searching and reading pages and databases, creating and updating pages, querying data sources, and reading or writing comments. Authorized by Teloa via OAuth (dynamic client registration + PKCE) with automatic token refresh.