jeremylongshore

Execute extract and use project memories from previous sessions for context-aware assistance. Use when recalling past decisions, checking project conventions, or understanding user preferences. Trigger with phrases like "remember when", "like before", or "what was our decision about".

Execute automatically formats and validates code files using Prettier and other formatting tools. Use when users mention "format my code", "fix formatting", "apply code style", "check formatting", "make code consistent", or "clean up code formatting". Handles JavaScript, TypeScript, JSON, CSS, Markdown, and many other file types. Trigger with relevant phrases based on skill purpose.

Configure Clerk CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Clerk tests into your build process. Trigger with phrases like "clerk CI", "clerk GitHub Actions", "clerk automated tests", "CI clerk", "clerk pipeline".

Troubleshoot common Clerk errors and issues. Use when encountering authentication errors, SDK issues, or configuration problems with Clerk. Trigger with phrases like "clerk error", "clerk not working", "clerk authentication failed", "clerk issue", "fix clerk".

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

Handle user data, privacy, and GDPR compliance with Clerk. Use when implementing data export, user deletion, or privacy compliance features. Trigger with phrases like "clerk user data", "clerk GDPR", "clerk privacy", "clerk data export", "clerk delete user".

Collect comprehensive debug information for Clerk issues. Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues. Trigger with phrases like "clerk debug", "clerk diagnostics", "clerk support ticket", "clerk troubleshooting".

Generate and configure Nixtla Skills using the CLI for forecasting workflows. Use when installing or updating skills. Trigger with 'install nixtla skills' or 'update nixtla'.

Generate benchmarking pipelines to compare forecasting models and summarize accuracy/speed trade-offs. Use when evaluating TimeGPT vs StatsForecast/MLForecast/NeuralForecast on a dataset. Trigger with "benchmark models", "compare TimeGPT vs StatsForecast", or "model selection".

Research and summarize Nixtla ecosystem updates and time-series forecasting content from the web and GitHub. Use when gathering release notes, recent changes, or best-practice references. Trigger with "Nixtla updates", "what's new with TimeGPT", or "find time-series papers".

Generate production-ready TimeGPT forecasting pipeline code from requirements. Use when scaffolding a pipeline with validation, logging, visualization, and repeatable runs. Trigger with "create TimeGPT pipeline", "build TimeGPT integration", or "generate forecast code".

Analyze Nixtla baseline forecasting results (sMAPE/MASE on M4 or other benchmark datasets). Use when the user asks about baseline performance, model comparisons, or metric interpretation for Nixtla time-series experiments. Trigger with "baseline review", "interpret sMAPE/MASE", or "compare AutoETS vs AutoTheta".

Orchestrate 6-phase changelog generation workflow with AI synthesis, multi-source data fetching (GitHub/Slack/Git), quality validation, and automated PR creation. Use when automating release notes, weekly changelogs, or documentation updates. Trigger with "generate changelog", "weekly changelog", or "automate release notes".

Analyze and explain TimeGPT forecast results in plain English. Generates executive summaries with driver analysis. Use when stakeholders need forecast explanations, board presentations, or compliance documentation. Trigger with "explain forecast", "why is the forecast", "forecast narrative".

Fine-tunes TimeGPT on custom datasets to improve forecasting accuracy. Use when TimeGPT's zero-shot performance is insufficient or domain-specific accuracy is needed. Trigger with "finetune TimeGPT", "train TimeGPT", "adapt TimeGPT".

Self-improving research loops with hypothesis generation, experiment design, and result analysis

Full-stack research and code generation pipeline - research, code, and create

Natural language web UI control — element detection, targeted interaction, and automated form filling

Public opinion analysis and sentiment at scale — sentiment scoring, stance detection, and multi-dimensional bias measurement.

Meta-specialist that auto-discovers and scaffolds new specialists from trending GitHub repos

Safe multi-language code execution via alibaba/OpenSandbox

Multi-agent financial analysis pipeline: fundamental analysis, technical indicators, and news sentiment scoring for any ticker symbol. Wraps patterns from virattt/ai-hedge-fund and ZhuLinsen/daily_stock_analysis.

Ensemble predictions via swarm intelligence with multi-model voting and consensus

Generates conventional commit messages from staged git diffs. Activates when the user requests a commit message and produces type(scope) subject format.

Runs the j-rig seven-layer binary evaluation on a Claude skill and reports a ship or no-ship rollout decision. Activates when a user asks to evaluate, grade, score, or gate a SKILL.md before release.

Generates comprehensive analysis reports from input data. Activates when analysis is requested and produces structured output.

I can help you do things.

Tests referenced file detection with both valid and broken references in the body.

Does stuff.

Generates conventional commit messages from staged git diffs. Activates when the user requests a commit message and produces type(scope) subject format.

the frontmatter fence below is never closed

A conformant demo skill used as a conform pass fixture.

Partner skill.

A demo skill.

A demo skill.

Run a research → enrich → outreach SDR campaign from inside Claude Code, fully local with your own data-provider + model keys. This is the ORCHESTRATOR: it dispatches phase sub-agents (research, enrich, draft) in fixed order, checkpoints with you between phases, and saves a validated run. Use when the user wants to prospect companies, build a lead list, research accounts, or draft personalized cold outreach (email or LinkedIn) over domains they name. Triggers: "run an outreach campaign", "prospect these companies", "research these domains", "draft cold emails to", "build me a lead list", "/intent-outreach".

Show which Intent Outreach data connectors are configured (have a bring-your-own key) versus skipped, with each one's tier. Use when the user asks which connectors or data providers are set up, whether a specific provider (apollo, hunter, …) is configured, or wants a preflight check before running a campaign. Triggers: "/outreach-connectors", "which connectors are configured", "connector status", "what data providers do I have".

Inspect or scaffold an Intent Outreach Report Profile — the local file of deterministic knobs (intake, filtering, tone/length, output formats, delivery) that shape a campaign. Use when the user wants to list existing profiles, see a named profile, or create a new one. Triggers: "/outreach-profile", "list report profiles", "show a report profile", "create an outreach profile".

Research one or more company domains (Intent Outreach Phase 1 only) — surface leads + contacts, with no enrichment or drafting. Use when the user wants quick account research, to find who works at a company, or to vet a domain list before committing to a full campaign. Triggers: "/outreach-research", "research these domains", "pull leads for a domain", "Phase 1 only".

Saves a single fact, decision, pattern, or convention into the governed knowledge brain so it can be recalled later — and (for admins) retires memories that are outdated. Admin-only and side-effecting: it writes to the governed corpus, so it never auto-fires — invoke it explicitly. Use when an admin wants the brain to remember something specific going forward without a full recompile, or to mark an old memory outdated. Trigger with "/brain-save".

Answers questions about Intent Solutions' own systems, decisions, runbooks, and conventions from the governed knowledge brain, returning a qmd:// citation for every claim — receipts, not recall. Use when a teammate asks what the team knows about its own architecture, infrastructure, decisions, or conventions (e.g. "what does our system map say about the Caddy block", "why did we pick Apache-2.0", "how does the brain auth work", "what is our deploy runbook"). Trigger with "/brain", "ask the brain", "what do we know about", "what does our system map say", or "check the team knowledge base".

Runs an end-of-session capture sweep for the governed knowledge brain: reviews what happened, classifies insights, checks for conflicts, and proposes governed memories via the teamkb MCP tools. Admin capture workflow that complements the one-shot /brain-save. Use when wrapping up a session with team-relevant discoveries, or when importing existing docs into the brain. Trigger with "/teamkb", "capture this session", or "sweep for team knowledge".

Saves a single fact, decision, pattern, or convention into the governed knowledge brain so it can be recalled later — and (for admins) retires memories that are outdated. Admin-only and side-effecting: it writes to the governed corpus, so it never auto-fires — invoke it explicitly. Use when an admin wants the brain to remember something specific going forward without a full recompile, or to mark an old memory outdated. Trigger with "/brain-save".

Answers questions about Intent Solutions' own systems, decisions, runbooks, and conventions from the governed knowledge brain, returning a qmd:// citation for every claim — receipts, not recall. Use when a teammate asks what the team knows about its own architecture, infrastructure, decisions, or conventions (e.g. "what does our system map say about the Caddy block", "why did we pick Apache-2.0", "how does the brain auth work", "what is our deploy runbook"). Trigger with "/brain", "ask the brain", "what do we know about", "what does our system map say", or "check the team knowledge base".

Runs an end-of-session capture sweep for the governed knowledge brain: reviews what happened, classifies insights, checks for conflicts, and proposes governed memories via the teamkb MCP tools. Admin capture workflow that complements the one-shot /brain-save. Use when wrapping up a session with team-relevant discoveries, or when importing existing docs into the brain. Trigger with "/teamkb", "capture this session", or "sweep for team knowledge".

Read-only daily email check-in over Gmail or Outlook. Syncs the latest messages into the local store, then triages them (P1–P4 priority with a one-line "why", action-type, urgency signals, and detected deadlines), summarizes long threads, groups by category, and surfaces the high-priority and needs-response items as a single digest. Takes NO actions — purely a morning "what needs me today" briefing. Use when you want to check your inbox, get a daily digest, see what is high priority or needs a response, or catch up on long email threads. Trigger with "/email-checkin", "check my inbox", "daily email digest", "what needs a response", "what's high priority in my email".

Teach IntentMail your projects, clients, and priorities in plain language, then translate that context into concrete filing/priority rules. Reads a human-written context file (context/projects.md), and for filing or prioritization intent ("anything from Acme is high priority and goes to the Clients folder") proposes the equivalent IntentMail rules, previews them as a dry-run, and only creates them on confirmation. Use when you want the inbox to understand your business context, set up auto-filing/auto-priority rules, file mail by project or client, or review/adjust existing rules. Trigger with "/email-project-context", "set up my email rules", "file mail by project", "make Acme high priority", "teach my inbox about my projects".

Take real inbox actions over Gmail or Outlook — mark read, archive, flag, move/relabel, draft replies, and (two-phase) delete — driven by triage. Safety-first: mutating operations preview a dry-run before executing, drafts are created but NEVER auto-sent, deletes are staged then committed separately, and every action is written to an audit log that supports rollback. Use when you want to act on your inbox: clear it, archive newsletters, flag what needs follow-up, draft replies to the items that need a response, or file mail into folders/labels. Trigger with "/email-triage-actions", "act on my inbox", "archive these", "flag for follow-up", "draft replies", "clean up my inbox", "move to folder".

Saves a single fact, decision, pattern, or convention into your governed knowledge brain so it can be recalled later — and retires memories that are outdated. Side-effecting: it writes to your durable corpus, so it never auto-fires — invoke it explicitly. Use when you want the brain to remember something specific going forward without a full recompile, or to mark an old memory outdated. Trigger with "/brain-save".

Answers questions about your own systems, notes, decisions, runbooks, and conventions from your governed knowledge brain, returning a qmd:// citation for every claim — receipts, not recall. Use when you want to know what your brain has captured about your own architecture, infrastructure, decisions, or conventions (e.g. "what does my system map say about the proxy", "why did I pick Apache-2.0", "what's my deploy runbook"). Trigger with "/brain", "ask the brain", "what do I know about", or "check my knowledge base".

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refre

Research and onboard new data sources for STCI, producing source profiles, collector stubs, and validation rules