.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/jeremylongshore/claude-code-plugins-plus-skills
home/skills/jeremylongshore/claude-code-plugins-plus-skills
jeremylongshore avatar

jeremylongshore/claude-code-plugins-plus-skills

36 skills

View on GitHub
$npx skills add jeremylongshore/claude-code-plugins-plus-skills
SkillInstalls
agency-osNotion-as-source-of-truth dispatch board for running your work like an AI agency.—auditUse when the user wants a code review on recent changes — quality, spec, security, or performance feedback.—backgroundUse when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs.—bridgeUse when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.ai web, or IDE extensions that don't…—buzz-devrelDeveloper relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event…—buzz-hnHacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with…—buzz-outreachMedia and podcast outreach personalizer — takes a story angle and target journalist or host list and produces personalized pitch emails per target.—cacheUse when the user wants to view, search, add, edit, prune, archive, or clear hyperflow memory entries.—deployUse when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked.—designUse when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity —…—dispatchUse when a task file exists in .hyperflow/tasks/ and workers need dispatching.—flushUse when the user wants to manually flush a deferred-commit queue from a prior or interrupted chain.—handoffUse when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run.—hyperflowUse when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, or another single-agent surface.—hyperflow-auditHyperflow code review. Use when the user wants the current diff, a commit, branch, or PR reviewed — verbs like audit, review, "check for issues", "security…—hyperflow-cacheHyperflow memory manager. Use to view, search, add, edit, prune, or clear hyperflow project memory — "show memory", "search memory for X", "clear memory",…—hyperflow-deployHyperflow ship phase. Use when the user is ready to release — verbs like ship, push, release, deploy, "cut a release", "ready to push".—hyperflow-designHyperflow design phase. Use when designing a UI / visual system or making a screen look good — verbs like "design the UI", "make it look good", "design the…—hyperflow-dispatchHyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, "wire…—hyperflow-planHyperflow planning phase. Use when a request needs shaping before code — a rough prompt to sharpen, an ambiguous idea to design, or a clear-enough task to…—hyperflow-scaffoldHyperflow project setup. Use when starting hyperflow in a new project or refreshing its cache — "init hyperflow", "set up hyperflow", "refresh hyperflow",…—hyperflow-statusHyperflow project status. Use to see current hyperflow state — "what is hyperflow doing", "show task progress", "where are we".—hyperflow-stickyHyperflow auto-routing mode. Use to control how aggressively hyperflow auto-routes — "make hyperflow sticky", "stop using hyperflow", "auto-route to…—hyperflow-traceHyperflow debugging. Use for bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports — verbs like debug, "fix it", solve, "why is X…—ink-briefContent brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal…—ink-clusterTopic cluster architecture builder — takes a core topic and maps the full cluster with 1 pillar page, 6-10 supporting posts, internal linking map, keyword…—ink-distributeContent distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with…—issueUse when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request.—planUse when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to…—prUse when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff range, posts findings as one batched review…—scaffoldUse when starting hyperflow in a new project, refreshing the .hyperflow/ cache, or installing auto-detection shims (AGENTS.md, CLAUDE.md).—shipwright-pipelineAutonomous app builder that converts plain-English descriptions into—statusUse when the user wants a one-screen view of current hyperflow project state — version, profile freshness, memory count, and live progress on every in-flight…—stickyUse when the user wants to set auto-routing mode: on (every task-shaped message routes), auto (intent-verb messages route — default), or off (no auto-routing).—traceUse when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports.—workflowUse when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide…—