Skip to content

discolike/discolike-skills / skills/setup

DiscoLike setup — connect the agent to DiscoLike. Use when no DiscoLike MCP tools are visible and `discolike` is not on PATH, when `discolike auth status` or `account usage` fails on auth, when the CLI on PATH is older than 0.4.1, or when the user asks to set up, connect, or log in to DiscoLike. Signs in, or opens an account when there is none.

DiscoLike setup

Two doors: the hosted MCP server (best when the client supports remote MCP) and the discolike CLI (best when shelling out). Either one signed in is enough. Work through the steps in order and stop at the first one that proves a working connection.

1. Is MCP already connected?

If tools named discover-similar-companies or account-status are in your tool list, call account-status. Success means DiscoLike is connected through MCP: name the plan and remaining quota in one line and stop. Skip the CLI steps unless the user wants the CLI too.

2. Is the CLI signed in?

discolike auth status; echo "exit_code=$?"

Read the exit code and the JSON, not any prose.

  • exit_code=0 with "valid": true: signed in. Run discolike --version; at 0.4.1 or later, stop. Older, go to step 3.
  • exit_code=3: a credential is missing or rejected. Go to step 4.
  • command not found: go to step 3.
  • exit_code=5: network. Say so and stop; nothing here fixes that.

3. Install or upgrade the CLI

The skills need discolike-cli 0.4.1 or later. Do not install packages yourself; ask the user to run one of these in their own terminal:

pip install --upgrade discolike-cli
uv tool install discolike-cli   # or: uv tool upgrade discolike-cli

Then confirm:

discolike --version; echo "exit_code=$?"

At 0.4.1 or later, go back to step 2. command not found right after installing means the install's script directory is not on PATH in this shell; have the user open a new shell.

4. Sign in, or open an account

Ask, with AskUserQuestion when available: does the user already have a DiscoLike account?

Yes, browser available:

discolike auth login

Opens the browser for OAuth and stores the session under ~/.config/discolike/. Over SSH or without a browser, discolike auth login --no-browser --port 8765 prints the URL to open elsewhere.

Yes, key in hand: ask the user to run discolike auth login --api-key <KEY> themselves, or set DISCOLIKE_API_KEY in their own shell. Never ask for the key in chat, never read it from a file they did not name, and never write it into a config file yourself.

No account: ask for the work email, first and last name, show the user the exact values, and run this only after they say yes.

discolike signup --email 'jane@acme.com' --first-name 'Jane' --last-name 'Doe'

Single-quote every value so spaces and shell characters in a name stay literal; a name with an apostrophe goes in double quotes instead. Nothing sensitive comes back. The person confirms by email, picks a plan, and then runs discolike auth login. Free-mail and disposable domains are rejected; a 409 means the account exists, so send them to log in. Stop here and tell the user what to do next; the rest of setup waits for the confirmed account.

5. Verify

discolike account usage --format json

Report the plan and remaining quota in one sentence. Then return to whatever the user asked for; if setup was the whole request, offer one concrete first task: a free discolike count for their ICP, or a 25-record discover sample.

Troubleshooting

SymptomCauseFix
discolike: command not found after step 3Install directory not on PATH in this shellOpen a new shell
auth status exit 3 right after loginExpired OAuth sessiondiscolike auth logout, then discolike auth login
Browser never opensHeadless or SSH sessiondiscolike auth login --no-browser --port <n> and forward the port
MCP tools missing after adding the serverClient needs a restart, or OAuth was not completedRestart the client, retry the authorization
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall