agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/setup-shorty/SKILL.md

setup-shorty

Skill0 starsChanged 9 days agoMITView on GitHub

Connects the Shorty MCP server to Claude and verifies it with one read-only call: where to connect in claude.ai, Claude Desktop, Cowork, or Claude Code, what the Shorty sign-in and consent screen asks, and how to recover when a tool is missing. Use when the user asks to 'set up Shorty', 'connect Shorty to Claude', 'install the Shorty connector', 'sign in to Shorty', 'why can't Claude see my Shorty data', 'Shorty tools are missing', or reports 'Tool not found' for a Shorty tool.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never ask the user for a Shorty password, API key, or access token in the chat.

    line 50
  2. Distinctive:

    Do not change Shorty settings on the user's behalf.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated from plugins/shorty/skills/setup-shorty/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

Set up Shorty

Connect the Shorty MCP server, confirm it answers, and fix the usual reasons a Shorty tool is missing. Sign-in and consent always happen in Shorty's own browser page, never in the chat.

Where to connect

Claude Code with this plugin

  1. The plugin already registers the shorty server. Run /mcp, pick the Shorty server, and choose Authenticate, or just ask a Shorty question and follow the sign-in link Claude opens.
  2. Without the plugin, add the server by hand: claude mcp add --transport http shorty https://aishorty.com/api/mcp, then authenticate from /mcp.
  3. A connector added on claude.ai is also available in Claude Code when you are signed in with the same claude.ai account, so there is no need to connect twice.

claude.ai, Claude Desktop, and Cowork

  1. Open the Shorty listing in the Connectors Directory: https://claude.ai/directory/connectors/shorty and select Connect. In the app you can also search the directory for "Shorty".
  2. Sign in to Shorty in the page that opens and approve the consent screen.
  3. On a Team or Enterprise plan, an Owner may need to approve the connector first; members without that permission see a Request button.

What the sign-in asks

Shorty asks you to sign in (the sign-in page is /login), then shows the scopes this connection may use: library, transcriptions, usage, jobs, docs, and the write scopes that start summary, transcript, and subtitle jobs. The write scopes use your plan quota. Consent is re-checked on every call, and you can revoke it under Settings > Connected AI Apps in Shorty.

Verify the connection

Make one read-only call and report what came back in a sentence.

Call shorty:get_usage_quota if it is listed by name. If only shorty:search_tools and shorty:execute_typescript are listed (Code Mode), call shorty:search_tools, then run shorty:execute_typescript with return await external_get_usage_quota({});. It returns the plan tier and remaining allowance. A normal answer means Shorty is connected; say so and continue with the user's task.

When a tool is missing

Most accounts see Code Mode: tools/list shows only shorty:search_tools and shorty:execute_typescript, and every Shorty tool is called inside the sandbox as external_<tool>.

  • "Tool not found" on a named tool: switch to shorty:search_tools then shorty:execute_typescript instead of retrying the direct call.
  • shorty:search_tools does not return the tool: its scope was not granted. Ask the user to disconnect and reconnect Shorty and approve that scope on the consent screen.
  • An error naming a setting or a plan: a Shorty setting or plan gate refused the call. Relay the message and any settings link it carries; do not retry around it.
  • No shorty tools at all, or an authentication error: the connector is not connected or the sign-in expired. Repeat the steps under "Where to connect".

Rules

  • Never ask the user for a Shorty password, API key, or access token in the chat. OAuth happens in the browser.
  • Do not change Shorty settings on the user's behalf. Settings that unlock writes are turned on by a signed-in person in Shorty.
  • The verification call reads only. Do not create, send, or publish anything while setting up.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.