ConcertoNotes
- 1.7k skills
- 0 followers
- 2 weeks ago last updated
- ▌ Ngs Fastq Qc · concertonotes bundleValidate FASTQ inputs, run local FastQC/MultiQC QC, interpret QC signals, and optionally execute fastp or Cutadapt trimming branches without overwriting raw reads.
- ▌ Scrna Seq Qc · concertonotes bundleProcess, quality-control, annotate, and visualize single-cell or single-nucleus RNA-seq datasets across tissues and species. Use when Codex needs to build, adapt, or review a general scRNA-seq QC pipeline; choose dataset-appropriate cell-level filters from QC distributions; run required scDblFinder-based doublet and ambient-RNA filtering; annotate cells with matched references or marker-based fallbacks; or generate global and per-group UMAP visualizations for large scRNA-seq datasets.
- ▌ Improve Skill · concertonotes bundleTurn plugin-eval findings into a concrete rewrite brief for a Codex skill. Use when the user already evaluated a skill and now wants Codex to improve it, especially after asking what to fix first.
- ▌ Build Business Case · concertonotes bundleBuild customer-led business cases, ROI narratives, value models, executive summaries, and customer-ready value stories from uneven customer context, metrics, transcripts, notes, and public evidence.
- ▌ Prepare For Meeting · concertonotes bundleCreate concise pre-meeting briefs and daily prep for customer meetings or the user's most important meeting of the day, using authoritative internal context plus supplementary public web enrichment.
- ▌ Prioritize Accounts · concertonotes bundlePrioritize rep-ready pipeline by ranking accounts, suppressing in-flight motion, selecting the best reachable contact, and producing a connector-grounded account action view plus a concise planning-only action package from CRM, user-provided lists, saved context, and optional enrichment evidence.
- ▌ Shopify Functions · concertonotes bundleShopify Functions allow developers to customize the backend logic that powers parts of Shopify. Available APIs: Discount, Cart and Checkout Validation, Cart Transform, Pickup Point Delivery Option Generator, Delivery Customization, Fulfillment Constraints, Local Pickup Delivery Option Generator, Order Routing Location Rule, Payment Customization
- ▌ Spreadsheets · concertonotes bundleUse this skill when a user requests to create, modify, analyze, visualize, or work with spreadsheet files (`.xlsx`, `.xls`, `.csv`, `.tsv`) or Google Sheets-targeted spreadsheet artifacts with formulas, formatting, charts, tables, and recalculation.
- ▌ Investigation Mode · concertonotes bundleOrchestrated debugging coordinator. Triggers on frustration signals (stuck, hung, broken, waiting) and systematically triages: runtime logs → workflow status → browser verify → deploy/env. Reports findings at every step.
- ▌ Routing Middleware · concertonotes bundleVercel Routing Middleware guidance — request interception before cache, rewrites, redirects, personalization. Works with any framework. Supports Edge, Node.js, and Bun runtimes. Use when intercepting requests at the platform level.
- ▌ Zoom Meeting Sdk Electron · concertonotes bundleZoom Meeting SDK for Electron desktop applications. Use when embedding Zoom meetings in an Electron app with the Node addon wrapper, JWT auth, join/start flows, settings controllers, and raw data integration.
- ▌ Using Git Worktrees · concertonotesUse when starting feature work that needs isolation from the current workspace, or when an implementation plan should run outside the active working tree.
- ▌ Agent Mail · concertonotes bundleUse when coordinating agents with Agent Mail locks, inboxes, threads, and conflict-prevention handoffs. Triggers: "agent-mail", "agent mail", "use when coordinating agents with".
- ▌ Agy Native · concertonotes bundleDrive AgentOps in AGY: loop, plugins, memory, evidence, scoped worktrees. Triggers: agy, antigravity, agy plugin, AGY evidence.
- ▌ Codex Exec · concertonotes bundleUse when running Codex workers or validators non-interactively through codex exec with evidence. Triggers:
- ▌ Heal Skill · concertonotes bundleRepair skill hygiene. Triggers: "heal-skill", "heal skill", "repair skill hygiene.".
- ▌ Explain Decision · concertonotesFetch the full reasoning behind an AxonFlow policy decision — matched policies, risk level, override availability, recent hit count
- ▌ Brooks Health · concertonotes bundleCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).
- ▌ Brooks Review · concertonotes bundlePR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.
- ▌ Skill Claw · concertonotes bundleOpenClaw instance administration — manage hosts across macOS, Ubuntu/Debian, Docker, OCI, and Proxmox
- ▌ Skill Deck · concertonotes bundleGenerate slide deck presentations from briefs — use when you need slides, pitch decks, or visual summaries
- ▌ Skill Ship · concertonotes bundlePackage and finalize completed work for delivery — use when a feature is done and ready to ship
- ▌ Context Pack · concertonotes bundleGenerate a compact first-pass repository briefing with context-pack. Use when work starts in an unfamiliar repo, when the user asks for orientation or high-signal files, when active changes need a compact summary, or when prompt budget matters.
- ▌ Dev Grill Docs · concertonotes bundlePrimary intake for fuzzy feature/product requirements before coding; prefer this over dev-spec for requirement alignment. Use when the user says or implies: 需求还不清楚, 先别写代码, 先帮我梳理/收敛/对齐/拆一下需求, 先问我问题, 明确范围/边界/验收标准, 写 PRD/spec/设计文档, 帮我设计, 写个方案, 这个需求怎么做, design this, scope this out. Also trigger on dev-grill-docs, grill-with-docs, 拷问需求, 拷问方案, 压测方案, 术语沉淀. Reads existing docs/code first, asks one focused question at a time, produces .claude/artifacts/designs/<feature>.md, and may update CONTEXT.md or docs/adr/ for durable terms/decisions. Does not implement code, fix bugs, or write implementation plans.
- ▌ Orchestrate · concertonotesTrigger: active multi-agent run. Handles inbox reading, dep resolution, message formatting, handoffs. Also provides status dashboard and intervention control via internal modes.
- ▌ Hermes Tweet · concertonotes bundleUse Xquik from Hermes Agent for X search, posting, replies, likes, retweets, follows, DMs, monitors, extraction jobs, draws, media, and trends.
- ▌ Systematic Debugging · concertonotesUse when encountering any bug, test failure, or unexpected behavior — before proposing fixes.
- ▌ Kunze Ad Setup · concertonotesCodex-native Amazon PPC setup workflow using Kunze's broader ecosystem-driven strategy. Use when the user wants LaunchFast-driven bulk-sheet generation with broad and phrase coverage, gap analysis, and a campaign package written to disk.
- ▌ Wilco Ad Setup · concertonotesCodex-native Amazon PPC setup workflow using Wilco's exact-match and analytics-first strategy. Use when the user wants stricter keyword control, exact-match campaigns, and a LaunchFast-driven bulk-sheet export.
- ▌ Roadmap Sync · concertonotes bundleDEPRECATED legacy root for RoadmapSmith slash workflows; use roadmap-maintain or roadmap-update.
- ▌ Sealos App Builder · concertonotes bundleBuild, adapt, and document apps that run inside Sealos Desktop using the Sealos app SDK. Use when creating a new Sealos app, integrating an existing web app into Sealos Desktop, wiring Sealos session data into business features, preparing local iframe-based debugging, or producing beginner-friendly Sealos app tutorials and starter implementations. Also triggers on "/sealos-app-builder".
- ▌ SEO Ecommerce · concertonotes bundleE-commerce SEO analysis: Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps. Combines on-page product SEO with marketplace data from DataForSEO Merchant API. Use when user says "ecommerce SEO", "product SEO", "Google Shopping", "marketplace SEO", "product schema", "Amazon SEO", "product listings", "shopping ads", or "merchant SEO".
- ▌ Spec Workflow · concertonotes bundleThis skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks", "write a PRD", "technical specification", or mentions "spec-driven development", "feature spec", "requirements phase", "design phase", or "tasks phase". Provides structured 3-phase workflow for feature development.
- ▌ Tool Advisor · concertonotes bundleDiscovers your full tool environment and amplifies prompts with capability awareness. Suggests optimal tool compositions as non-binding options. Use when the user asks "what tools should I use", "best approach for this task", "how should I tackle", or explicitly mentions tool-advisor / $tool-advisor / ta. Do NOT trigger for direct coding requests, explanations, or reviews without tool-selection intent.
- ▌ Book Genre Creator · concertonotesMeta-skill that references all available genres, agents, and skills to help users define and create any genre — including custom genres not yet supported.
- ▌ Writers Loop · concertonotes bundleUse when working on substantial writing artifacts where structure, audience fit, critique, revision, translation, style learning, or decision-backed preference learning matters; also when learning reusable writing style from the user's own writing or permitted reference samples.
- ▌ Airtable Overview · concertonotes bundleExplains what Airtable is and how data is structured — bases, tables, fields, records, views, automations, and interfaces. Use when you need context about the Airtable data model.
- ▌ Telemetry · concertonotes bundleAdd and verify lightweight macOS runtime telemetry. Use when wiring Logger events or inspecting logs for windows, sidebars, menus, and actions.
- ▌ Fix Finding · concertonotes bundleUse when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
- ▌ Capital Allocation · concertonotes bundleDeep dive into capital deployment, buybacks, dividends, and shareholder yield
- ▌ Design Kpis · concertonotes bundleDesign KPI frameworks, set targets, and develop measurement plans that help teams make product or business decisions. Use when success metrics, drivers, guardrails, targets, or measurement approach need to be defined or improved. Use $metric-diagnostics when the task is to explain why an existing metric moved.
- ▌ Phaser 2d Game · concertonotes bundleImplement 2D browser games with Phaser. Use when the user wants a Phaser, TypeScript, and Vite stack for scenes, gameplay systems, cameras, sprite animation, and DOM-overlay HUD patterns.
- ▌ Gh Address Comments · concertonotes bundleAddress actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use the GitHub app for PR metadata and flat comment reads, and use the bundled GraphQL script via `gh` whenever thread-level state, resolution status, or inline review context matters.
- ▌ Google Sheets · concertonotes bundleAnalyze and edit connected Google Sheets with range precision. Use when the user wants to create Google Sheets, find a spreadsheet, inspect tabs or ranges, search rows, plan formulas, create or repair charts, clean or restructure tables, write concise summaries, or make explicit cell-range updates.
- ▌ Netlify AI Gateway · concertonotes bundleGuide for using Netlify AI Gateway to access AI models. Use when adding AI capabilities or selecting/changing AI models. Must be read before choosing a model. Covers supported providers (OpenAI, Anthropic, Google), SDK setup, environment variables, and the list of available models.
- ▌ Netlify Frameworks · concertonotes bundleGuide for deploying web frameworks on Netlify. Use when setting up a framework project (Vite/React, Astro, TanStack Start, Next.js, Nuxt, SvelteKit, Remix) for Netlify deployment, configuring adapters or plugins, or troubleshooting framework-specific Netlify integration. Covers what Netlify needs from each framework and how adapters handle server-side rendering.
- ▌ Ngs Scrna Seq · concertonotes bundleRoute single-cell or single-nucleus RNA-seq FASTQs to public count-generation workflows and defer post-count matrix QC, annotation, clustering, and UMAP analysis to the embedded scrna-seq-qc skill.
- ▌ Evaluate Skill · concertonotes bundleEvaluate a local Codex skill in engineer-friendly terms. Use when the user says "evaluate this skill", "give me an analysis of the game dev skill", "audit this skill", "why did this score that way", "what should I fix first", or asks for a skill-specific report before benchmarking it.
- ▌ Get Context · concertonotes bundleMandatory design-brief gate for Product Design build and design workflows. Use before ideation, prototyping, image-to-code builds, redesigns, or product UI work to clarify missing product, visual, and interactivity context or play back the supplied brief before proceeding.
- ▌ Url To Code · concertonotes bundleClone a live URL as a runnable frontend-only local app using Browser/Chrome source evidence after Product Design get-context has confirmed the design brief.
- ▌ Render Static Sites · concertonotes bundleDeploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.
- ▌ Render Web Services · concertonotes bundleConfigures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
- ▌ Find Customer Quotes · concertonotes bundleRetrieve theme-specific customer or prospect quotes from transcripts, call notes, or exported recordings using transcript-first evidence and explicit speaker-confidence rules.
- ▌ Follow Up After Call · concertonotes bundleTurn a recent customer, partner, or important internal call transcript or grounded call notes into a seller-ready follow-up package with a recap, next steps, external comms when applicable, CRM next steps when applicable, and an internal follow-up draft.
- ▌ Slack Reply Drafting · concertonotes bundleDraft Slack replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.
- ▌ Superhuman Mail · concertonotes bundleUse Superhuman Mail MCP for email and calendar workflows such as searching inboxes, reading threads, drafting or sending mail, managing labels, checking read statuses, finding availability, and creating or updating events.
- ▌ Teams Reply Drafting · concertonotes bundleDraft Microsoft Teams replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.
- ▌ Sign In With Vercel · concertonotes bundleSign in with Vercel guidance — OAuth 2.0/OIDC identity provider for user authentication via Vercel accounts. Use when implementing user login with Vercel as the identity provider.
- ▌ Zoom Virtual Agent Android · concertonotes bundleZoom Virtual Agent Android integration via WebView. Use for Java/Kotlin bridge callbacks, native URL handling, support_handoff relay, and lifecycle-safe embedding.
- ▌ Toil Mining · concertonotes bundleMine usage history (cass, rtk, shell) for repeated toil, score frequency x pain, emit ranked candidates for automation-shape-routing. Use when rituals repeat by hand.
- ▌ Run Task · concertonotesExecute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task <task>. Uses get_task, update_task, create_task_comment.
- ▌ Run Work · concertonotesExecute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work <work-unit>. Uses get_work_unit, list_tasks, update_task, get_work_unit_progress.
- ▌ Pre Execute Check · concertonotesCheck AxonFlow governance policy before executing commands, writing files, or modifying any state. Also scan file content for PII before writing. Use before any tool call that creates, modifies, or deletes data.
- ▌ Flow Define · concertonotes bundleMulti-AI requirements scoping using available external providers (Double Diamond Define phase)
- ▌ Skill Audit · concertonotes bundleAudit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review
- ▌ Skill Debug · concertonotes bundleDebug issues methodically — use when stuck on errors, test failures, or unexpected behavior
- ▌ Honcho Memory · concertonotesPersistent cross-session memory via Honcho — recall what you know about the user before working, and save durable insights after.
- ▌ Dev Code Review · concertonotes bundleUse when reviewing uncommitted or staged git changes before commit. Trigger on: 帮我 commit, 我要 commit, commit 一下, 准备提交, pre-commit, 提交前检查, 看下这次修改, commit 前看一下, I want to commit, let's commit, review my changes. Checks conventions, functional correctness, security/reliability/performance hotspots, wiring, comments, and dead code; emits a commit message only when READY. Does not mutate the working tree. Route to dev-commit-writer only when the user explicitly asks to skip review or wants only a commit message.
- ▌ Distill · concertonotes bundleUse when user wants to reduce noise, verbosity, or redundancy in markdown or text files. Use when user says distill, compress, clean up, tighten, denoise, reduce entropy, improve signal-to-noise ratio, or make text more concise. Accepts a file path, a directory (distills all .md/.txt files in it), or no argument (distills all .md/.txt files in the current directory).
- ▌ Threat Model · concertonotesThreat modeling and attack surface analysis. Use when assessing security boundaries, modeling threat actors, or generating threat scenarios.
- ▌ Hol Guard · concertonotesUse when setting up HOL Guard, protecting local AI harnesses, reviewing Guard approvals or receipts, scanning Codex plugins, skills, MCP servers, marketplace packages, or running plugin-scanner verification before release.
- ▌ Receiving Code Review · concertonotesUse when review findings arrive — verify each claim against the codebase and HOTL contracts before making changes. Governs how agents respond to review feedback.
- ▌ Batch Extraction · concertonotesUse when extracting from many files at once with shared config, bounded parallelism, per-file overrides, and error recovery. Covers the `batch` command, `--file-configs`, `--max-concurrent`, and output layout.
- ▌ Picking A Format · concertonotesUse when choosing an output format for extracted documents — text, markdown, djot, html, or JSON. Maps consumer (LLM, parser, archive) to the right `--format` / `--content-format` pair.
- ▌ Crawling A Site · concertonotesUse when the user wants to follow links across a domain and capture every reachable page as Markdown. Covers `kreuzcrawl crawl` with depth, page caps, concurrency, rate limiting, domain scoping, robots, and output selection.
- ▌ Serving The API · concertonotesUse when the user wants a long-running HTTP service for scrape/crawl/map instead of one-shot CLI calls or the MCP server — for example wiring kreuzcrawl into other apps over REST. Covers `kreuzcrawl serve`, the Firecrawl-v1-compatible endpoints, `--host`/`--port`, and when to prefer it.
- ▌ Fastmcp Django · concertonotes bundleUse when adding, changing, deploying, testing, or debugging FastMCP MCP servers in existing Django apps, including ASGI mounting, stdio or sidecar servers, Django ORM access from MCP tools, auth and permissions, Streamable HTTP deployment, and MCP client tests.
- ▌ Daily · concertonotes bundleUse this skill when creating today's daily note in the Meta-Vault (03-daily/YYYY-MM-DD.md) with valid vaultFrontmatterSchema-compliant YAML frontmatter. Idempotent: re-running on the same day opens the existing note instead of overwriting. Use when starting a work day, capturing scratch notes, or bootstrapping the inbox flow.
- ▌ Grill · concertonotes bundleUse when the user wants a plan, design, or PRD stress-tested before any build — relentlessly interrogates one decision at a time, grounds every question in the codebase, hunts contradictions against the domain language and the code, and challenges the load-bearing assumptions. Triggered by "grill me", "stress-test this plan", "poke holes in my design". Composable — run standalone or as an adversarial pass before /plan feature.
- ▌ Create Branch · concertonotes bundleUse when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
- ▌ Github Issues · concertonotes bundleUse when filing a bug, requesting a feature, creating an issue, or updating issue details. Manages GitHub issues with templates, formatting, and auto-assignment.
- ▌ Naming Format · concertonotes bundleUse when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns.
- ▌ Vidseeds Projects · concertonotesUse for VidSeeds MCP project workflows — create a project from YouTube, list/get/snapshot, regenerate metadata (sync or async), translate metadata, apply thumbnails, and update per-platform config before publish.
- ▌ Zagrosi Plan · concertonotes bundleCreate a research-backed, reviewed, sectionized Zagrosi Forge TDD implementation plan from a markdown spec. Use for complex features, ambiguous requirements, architecture-heavy work, or any request to plan before coding with research, interviews, tests, review, and implementation sections.
- ▌ Triage Issue · concertonotes bundleIntelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.
- ▌ Build Report · concertonotes bundleBuild polished analytical reports for executive, product, business, and technical audiences, and act as the completion contract for Data Analytics report runs. Use when the final artifact needs an answer-first narrative, evidence-backed findings, charts/tables, caveats, source metadata, and either an MCP app report or an HTML report with Seaborn-generated charts.
- ▌ Deepnote Notebooks · concertonotesUse when reading, reviewing, inspecting, or reasoning about hosted Deepnote notebooks, blocks, inputs, SQL, Python, or notebook outputs through the Deepnote app tools.
- ▌ Codex Expo Run Actions · concertonotes bundleWire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions. Use when the user wants the Codex app Run button, build/run actions, action buttons, or a stable Expo start/run workflow from Codex.
- ▌ Figma Create New File · concertonotes**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `create_new_file` tool call. NEVER call `create_new_file` directly without loading this skill first. Trigger whenever the user wants a new blank Figma file — a new design, FigJam, or Slides file — or when you need a fresh file before calling `use_figma`. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review)
- ▌ Figma Generate Design · concertonotesUse this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.
- ▌ Sprite Pipeline · concertonotes bundleGenerate and normalize 2D sprite animations. Use when the user asks for full-strip generation from approved source frames, consistent anchor and scale normalization, or preview assets for browser-game animation.
- ▌ Hyperframes CLI · concertonotes bundleHyperFrames CLI tool — hyperframes init, lint, inspect, preview, render, transcribe, tts, doctor, browser, info, upgrade, compositions, docs, benchmark. Use when scaffolding a project, linting, validating, inspecting visual layout in compositions, previewing in the studio, rendering to video, transcribing audio, generating TTS, or troubleshooting the HyperFrames environment.
- ▌ Moody S Explore MCP · concertonotes bundleDiscover and safely explore Moody's MCP tools. Use when the user wants to see what Moody's data is available, verify MCP connectivity, look up an entity, or run a lightweight ratings/research probe before deeper analysis.
- ▌ Fund Comparison · concertonotes bundleUse when comparing 2 to 4 funds or ETFs with Morningstar ratings, returns, risk, and holdings data.
- ▌ Fund Summarizer · concertonotes bundleUse when summarizing a fund or ETF with Morningstar ratings, returns, risk, holdings, fees, and caveats.
- ▌ Neon Postgres · concertonotes bundleGuides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
- ▌ Outlook Email · concertonotes bundleTriage Outlook mail, extract tasks, clean up subscriptions, draft responses, and route shared mailbox work. Use when the user asks to inspect an Outlook inbox or thread, summarize open actions and deadlines, clean up newsletters, draft replies or forwards, organize mailbox follow-up work, or act on a delegated/shared Outlook mailbox.
- ▌ Evaluate Plugin · concertonotes bundleEvaluate a local Codex plugin in engineer-friendly language. Use when the user says "evaluate this plugin", "audit this plugin", "why did this score that way", "what should I fix first", "help me benchmark this plugin", or asks for a plugin-wide report before comparing versions.
- ▌
- ▌ Get Rep Call Feedback · concertonotes bundleCompare one rep’s call history against peer examples to extract repeatable best practices and produce evidence-backed coaching feedback.