MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
A skill your agent uses 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).
Install Sticky
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sticky --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/sticky .claude/skills/sticky && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sticky" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/sticky into .claude/skills/sticky/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sticky", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/stickyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sticky --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/sticky .agents/skills/sticky && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sticky" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/sticky into .agents/skills/sticky/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sticky", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sticky --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/sticky .cursor/skills/sticky && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sticky" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/sticky into .cursor/skills/sticky/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sticky", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/hyperflow/skills/sticky--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sticky --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/sticky .gemini/skills/sticky && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sticky" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/sticky into .gemini/skills/sticky/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sticky", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stickyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/sticky .github/skills/sticky && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sticky" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/sticky into .github/skills/sticky/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sticky", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sticky --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/sticky .opencode/skills/sticky && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sticky" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/sticky into .opencode/skills/sticky/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sticky", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sticky- GitHub stars
- 2.8k
- Token cost
- ~2.6k tokens
- SKILL.md length
- 950 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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).
- Works in 5 steps: Chat-shaped messages (questions about… → Task-shaped messages (any verb-led… → Bug reports ("X is broken", "Y test… → …
- The user wants to set auto-routing mode: on (every task-shaped message routes)
- SKILL.md covers Subcommands, State persistence, Subcommand Details and Behavioural contract, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sticky is an agent skill from jeremylongshore/tons-of-skills-marketplace. Use 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). Intent-detection runs by default; use this skill to expand to full sticky or disable entirely. Trigger with /hyperflow:sticky, "make hyperflow sticky", "stop using hyperflow", "is hyperflow sticky", "auto-route to hyperflow", "disable hyperflow auto-routing".
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code
It sits in Agent Workflows. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- The user wants to set auto-routing mode: on (every task-shaped message routes)
- Auto (intent-verb messages route — default)
- Off (no auto-routing)
- Expand to full sticky
Example prompts
- “make hyperflow sticky”
- “stop using hyperflow”
- “is hyperflow sticky”
- “/sticky”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(rm:*), Bash(ls:*)
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Chat-shaped messages (questions about prior output, "yes" / "no" answers to a pending gate, acknowledgments like "ok"/"thanks", short…
- Task-shaped messages (any verb-led request for new work: "add X", "fix Y", "refactor Z", "build", "implement", "create", "design", "scope…
- Bug reports ("X is broken", "Y test fails", "Z throws…") → invoke /hyperflow:trace.
- Review requests ("review this", "audit the diff", "any issues?") → invoke /hyperflow:audit.
- Ship intent ("ship it", "push", "release", "deploy") → invoke /hyperflow:deploy.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(rm:*)Bash(ls:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Sticky loads about 2.6k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 950 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 950 words, ~2,641 tokens.
Download SKILL.mdSave it as
.claude/skills/sticky/SKILL.md (or your agent's skills folder).- name
- sticky
- description
- Use 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). Intent-detection runs by default; use this skill to expand to full sticky or disable entirely. Trigger with /hyperflow:sticky, "make hyperflow sticky", "stop using hyperflow", "is hyperflow sticky", "auto-route to hyperflow", "disable hyperflow auto-routing".
- allowed-tools
- Read, Write, Edit, Bash(rm:*), Bash(ls:*)
- compatibility
- Designed for Claude Code
- argument-hint
- <on|auto|off|status>
- version
- 4.9.0
- license
- MIT
- tags
- session, automation, routing
Sticky
Set per-project auto-routing mode. Three states:
| State | Default? | Behavior |
|---|---|---|
auto | yes (when .sticky absent) | Intent-detection routing — messages containing chain-starter verbs (audit, debug, fix, brainstorm, scope, deploy, review, …) auto-route. Pure conversation passes through. |
on | — | Full sticky — every task-shaped message routes, even without explicit intent verbs |
off | — | All auto-routing disabled — only explicit /hyperflow:* slash commands trigger chains |
Intent-detection is the floor — the user gets it without any opt-in (the orchestrator scans every user message for chain-starter verbs and routes when matched). Sticky on raises the ceiling; sticky off lowers the floor.
Full doctrine: DOCTRINE.md Layer 1 auto-routing clause (intent verb taxonomy + routing contract + bypass patterns).
Subcommands
| Subcommand | Description |
|---|---|
on | Set state: on — full sticky routing on every task-shaped message |
auto | Set state: auto — intent-verb routing only (the default) |
off | Set state: off — disable ALL auto-routing including intent detection |
status | Show current state (on / auto / off / when toggled) |
Default subcommand when none provided: status.
State persistence
Sticky state is stored at .hyperflow/.sticky (project-scoped, gitignored). File format:
state: on
since: 2026-05-17T14:30:00Z
trigger: user-mention # or: explicit-toggle | session-defaultThe session-start hook reads this file and prints a one-line advisory when sticky is on (Sticky mode: ON since 2026-05-17 14:30 — task-shaped messages auto-route through hyperflow). Sticky persists across sessions until explicitly toggled off.
Subcommand Details
on
Write .hyperflow/.sticky with state: on + ISO-8601 timestamp + trigger: explicit-toggle. Print:
Sticky mode: ON (full routing)
Every task-shaped message now routes through hyperflow, even without intent verbs.
Disable with /hyperflow:sticky off · or relax to verb-only routing with /hyperflow:sticky auto.auto
Write .hyperflow/.sticky with state: auto + timestamp. This is the default state when no file exists; explicitly setting it is useful after off to re-enable intent-detection without going to full sticky. Print:
Sticky mode: AUTO (intent-detection routing, default)
Messages containing chain-starter verbs (audit, debug, fix, brainstorm, scope, deploy, review, …) auto-route.
Pure conversation passes through. Expand to full routing with /hyperflow:sticky on.off
Replace .hyperflow/.sticky contents with state: off + timestamp. (Keep the file rather than delete so the session-start hook can show recent history.) Print:
Sticky mode: OFF
All auto-routing disabled — even intent verbs (audit, debug, fix, brainstorm, …) will no longer route.
Use explicit /hyperflow:* invocations. Re-enable with /hyperflow:sticky auto or /hyperflow:sticky on.status
Read .hyperflow/.sticky. Print one line:
Sticky mode: ON since 2026-05-17 14:30 (trigger: user-mention)or:
Sticky mode: AUTO since 2026-05-17 14:30 (trigger: default · intent-detection routing)or:
Sticky mode: OFF (last changed: 2026-05-16 09:12)or, if file absent:
Sticky mode: AUTO (default · file not yet written · intent-detection routing active)Behavioural contract
When sticky is ON, the orchestrator MUST follow this routing on every new user message:
- Chat-shaped messages (questions about prior output, "yes" / "no" answers to a pending gate, acknowledgments like "ok"/"thanks", short clarifications) — pass through normally, no chain routing.
- Task-shaped messages (any verb-led request for new work: "add X", "fix Y", "refactor Z", "build", "implement", "create", "design", "scope out", "decompose", "ship") — auto-route:
- New work (whether the user asks what / should we or describes how and names concrete files / functions) → invoke
/hyperflow:planwith the user's message asARGUMENTS. Plan internally bounces past the design phase straight to decomposition when the request is already clear. - Existing task file referenced (e.g. "resume the auth task") → invoke
/hyperflow:dispatchwith the matching slug.
- New work (whether the user asks what / should we or describes how and names concrete files / functions) → invoke
- Bug reports ("X is broken", "Y test fails", "Z throws…") → invoke
/hyperflow:trace. - Review requests ("review this", "audit the diff", "any issues?") → invoke
/hyperflow:audit. - Ship intent ("ship it", "push", "release", "deploy") → invoke
/hyperflow:deploy.
The routing decision is made silently — print one short line (Routing to /hyperflow:plan (sticky mode) …) and invoke. Don't ask the user to confirm the routing (that would be an invented gate per DOCTRINE rule 8). The Step 0 chain-mode question still fires inside the routed skill.
Override: if the user message starts with / (any slash command) OR contains "without hyperflow" / "skip hyperflow" / "don't route" → bypass routing for that message; respond directly.
Show full SKILL.md (444 more words)Show less
Activation triggers
Intent-detection routing (state: auto) is the default — active for every project without any user action. The orchestrator scans every user message for chain-starter verbs (per the DOCTRINE intent verb taxonomy) and routes when matched. No file write needed.
Upgrades and downgrades:
- Upgrade to full sticky (
on):- Explicit: user runs
/hyperflow:sticky on. - Implicit: user mentions the word "hyperflow" in a non-slash-command message AND
.hyperflow/.stickydoes not exist OR isauto. Orchestrator writesstate: on · trigger: user-mention · since: <ISO-8601>and printsSticky mode: ON (upgraded from auto, activated by mention). Disable with /hyperflow:sticky off.
- Explicit: user runs
- Downgrade to intent-only (
auto): user runs/hyperflow:sticky auto. - Disable entirely (
off): user runs/hyperflow:sticky off. Disables intent detection too — only explicit/hyperflow:*slash commands route after this.
State is never silently changed by the orchestrator. Only the user's explicit /hyperflow:sticky <state> invocation (or the one-time implicit hyperflow-mention upgrade) modifies .hyperflow/.sticky.
Anti-patterns (when sticky is ON)
- Asking the user "should I route this to hyperflow?" — that's an invented gate; the user already opted in via sticky
- Skipping the Step 0 chain-mode question inside the routed skill — sticky controls routing, not gates
- Routing chat-shaped messages — answering a question shouldn't fire a chain
- Routing messages that start with
/— those are explicit slash commands; honor them as-is - Echoing the routing decision as a long paragraph — one short line is enough (
Routing to /hyperflow:plan (sticky mode) …)
Flow
- Parse subcommand from invocation (default:
status). - Read
.hyperflow/.sticky(if absent, treat as empty). - Execute subcommand: write the file (
on/off) or print state (status). - Print confirmation.
Overview
/hyperflow:sticky toggles per-project sticky-session routing. It does not itself perform routing — that's the orchestrator's behavioral contract when sticky is ON. This skill is the user-facing on/off switch and status reader.
Prerequisites
.hyperflow/directory writable. If absent, the skill creates.hyperflow/and writes.stickyinside.
Instructions
See Subcommands and Behavioural contract. Summary:
- Parse subcommand (default
status). - Read or write
.hyperflow/.stickyper the chosen subcommand. - Print one-line confirmation.
When sticky is ON, the orchestrator routes per the Behavioural contract on every subsequent user message — this skill itself isn't re-invoked, the contract lives in DOCTRINE.
Output
Single one-line status per subcommand (on / off / status). No multi-line output.
Error Handling
| Failure | Behavior |
|---|---|
.hyperflow/ missing | Create the directory, then write .sticky. |
.hyperflow/.sticky exists but malformed | Print one-line warning + treat as OFF. Backup the malformed file to .sticky.bak. |
Invalid subcommand (not on/off/status) | Print the valid subcommand list and exit. |
Examples
Enable sticky mode
/hyperflow:sticky on
Sticky mode: ON
Task-shaped messages now auto-route through /hyperflow:plan (which bounces straight to decomposition when the design is clear).
Chat-shaped messages (questions, answers, acknowledgments) still pass through normally.
Disable with /hyperflow:sticky off.Sticky activates from a casual mention
You: hey, let's use hyperflow for the next feature
[orchestrator: detects "hyperflow" mention, .hyperflow/.sticky doesn't exist yet]
Sticky mode: ON (activated by mention)
Task-shaped messages now auto-route. Disable with /hyperflow:sticky off.
You: add a search bar to the dashboard with debounced input
[orchestrator: task-shaped, clear request → routes to /hyperflow:plan]
Routing to /hyperflow:plan (sticky mode) …Check status
/hyperflow:sticky status
Sticky mode: ON since 2026-05-17 14:30 (trigger: user-mention)Bypass for one message
You: without hyperflow, just tell me what hooks.json controls
[orchestrator: contains "without hyperflow" → bypass for this message]
hooks.json declares the session lifecycle hooks the plugin registers with Claude Code…Disable sticky
/hyperflow:sticky off
Sticky mode: OFF
Task-shaped messages will no longer auto-route. Use explicit /hyperflow:* invocations.Resources
- DOCTRINE.md — Layer 1 sticky-session clause (the behavioural contract the orchestrator follows when sticky is ON).
- output-style.md — one-line confirmation format.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/ai-agency/hyperflow/skills/sticky of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Sticky next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sticky this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.6k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Sticky
What does Sticky do?
A skill your agent uses 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). Sticky is an agent skill from jeremylongshore/tons-of-skills-marketplace. Use 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).
When should I use Sticky?
Sticky fits situations like: the user wants to set auto-routing mode: on (every task-shaped message routes); auto (intent-verb messages route — default); off (no auto-routing); expand to full sticky.
How do I install Sticky in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a claude-code`. Or copy the skill folder (plugins/ai-agency/hyperflow/skills/sticky in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/sticky in your project. Claude Code loads it when a task matches its description.
How do I install Sticky in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a codex`. Or copy the skill folder (plugins/ai-agency/hyperflow/skills/sticky in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/sticky in your project. Codex loads it when a task matches its description.
Can I use Sticky in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sticky -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sticky, .gemini/skills/sticky, .github/skills/sticky and .opencode/skills/sticky in your project.
What does Sticky need to run?
SKILL.md names no scripts, command-line tools or credentials: Sticky is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(rm:*), Bash(ls:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Sticky access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sticky safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sticky use?
Sticky is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sticky use?
About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sticky?
Skills that share tags, products or a category with Sticky: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sticky?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.