agentsclimarketplace

Getting started

Skill tough-tongue/toughtongue-skills/skills/getting-started

Agent skills and MCP server for Tough Tongue AI. Create voice-agent scenarios, refine them from real transcripts, and analyze session performance from Claude Code, Codex, or Cursor.

Install
npx -y skills add tough-tongue/toughtongue-skills --skill getting-started

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Onboard a user to the Tough Tongue AI plugin: verify the MCP connection and PAT, look at what's in their account, and route them into their first workflow. This skill should be used when the user says "get started with Tough Tongue AI", "set up Tough Tongue AI", "is my Tough Tongue AI MCP working", "test my Tough Tongue AI connection", "what can I do with Tough Tongue AI", or has just installed the plugin. Not for creating, refining, or analyzing scenarios directly — hand off to scenario-creator, scenario-refiner, or session-analyst for those.

SKILL.md

3.4 KB, as published. Nobody here has run it

Getting Started with Tough Tongue AI

Verify the setup, orient around the user's account, and launch their first journey. Keep each step short — this is a welcome mat, not a manual.

Step 1: Verify the connection

Call the ttai MCP tool list_organizations.

  • Tools not found — the MCP server is not registered. Ask how they installed:
    • Plugin install: restart the agent app fully and start a new thread; the plugin registers the server via its bundled .mcp.json.
    • Skills-only install (skills.sh / Cursor): register manually — codex mcp add ttai --url https://api.toughtongueai.com/api/public/mcp --bearer-token-env-var TTAI_PAT (Codex) or claude mcp add --transport http ttai https://api.toughtongueai.com/api/public/mcp --header "Authorization: Bearer ${TTAI_PAT}" (Claude Code).
  • 401 / auth error — the PAT is not visible to the agent process. Walk through: create a token at https://app.toughtongueai.com/developer, export TTAI_PAT="<token>" in the shell profile, on macOS also launchctl setenv TTAI_PAT "$TTAI_PAT", then fully quit and reopen the agent app. NEVER ask the user to paste the token into the chat.
  • Success — report what came back: personal account only, or organizations (name them). Explain that org work needs org_id passed to tools, and this happens automatically in the other skills.

Step 2: Orient around the account

Call list_scenarios, and list_sessions with a small limit.

Summarize in 2-3 sentences what exists: how many scenarios, whether sessions have been run, whether analyses are present. This decides the recommended first journey below.

Step 3: Launch the first journey

Offer the paths that fit what Step 2 found, then invoke the matching skill:

Account stateRecommendSkill
Empty (no scenarios)Create a first practice scenario from a brief, URL, or call transcriptscenario-creator
Scenarios but few sessionsShare a practice link; or create a scenario for an upcoming meetingscenario-creator
Sessions with analysesTeam/scenario performance reportsession-analyst
Low-scoring or complained-about scenarioDiagnose and fix it from real transcriptsscenario-refiner

Close by showing 2-3 of these prompts as things to try next (pick the ones matching their account state):

  • "Pull the last 3 calls from Gong where we lost on pricing and create a practice scenario for that objection."
  • "For my discovery-call scenario, pull the last 50 sessions — what are the top 5 improvement areas?"
  • "Pull the 5 lowest-scoring sessions for our onboarding scenario and fix the scenario."
  • "I have a call with [name] from [company] in 30 minutes — create a quick practice scenario so I can rehearse."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.