Findings & checks · 1 flagged
MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · docs/migrations/livekit.md
A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.
- Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
- Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.
Trace & refs
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
spekoai-mcp
Model Context Protocol server for SpekoAI. The hosted server exposes one authenticated endpoint:
https://mcp.speko.ai/mcpIt supports OAuth for interactive MCP clients and Speko API keys for clients that can send custom request headers.
Install in an MCP client
OAuth-capable clients:
{
"mcpServers": {
"spekoai": {
"url": "https://mcp.speko.ai/mcp"
}
}
}API-key clients:
{
"mcpServers": {
"spekoai": {
"url": "https://mcp.speko.ai/mcp",
"headers": {
"Authorization": "Bearer sk_live_xxx"
}
}
}
}Surfaces
The hosted server exposes the operational tools below plus a docs self-serve surface: the docs.search tool (full-text search over bundled Speko docs) and the spekoai://docs/index + spekoai://docs/{slug} resources. MCP prompts, components, and scaffolding tools are not advertised.
Tool names use domain/action dot notation for client grouping.
Account
organization.getcredits.balance.getcredits.ledger.listusage.summary.get
Agents and Tools
agents.listagents.createagents.getagents.updateagents.deleteagents.tools.listagents.tools.createagents.tools.getagents.tools.updateagents.tools.delete
Versions, Sessions, and Calls
agents.deployagents.rollbackagents.versions.listsessions.createsessions.phone.createsessions.listsessions.getsessions.transcript.getsessions.recording.getagents.calls.listcalls.getcalls.recording.get
Phone Numbers, Knowledge Bases, and Evals
phone_numbers.listphone_numbers.available.searchphone_numbers.createphone_numbers.getphone_numbers.updatephone_numbers.deleteknowledge_bases.createknowledge_bases.listknowledge_bases.getknowledge_bases.deleteknowledge_bases.documents.listknowledge_bases.documents.createknowledge_bases.documents.getknowledge_bases.documents.deleteknowledge_bases.documents.finalizeagents.evals.listagents.evals.createagents.evals.runevals.get
Build and Migration Helpers
migration.workspace.inspectmigration.session_config.buildmigration.external_config.parsemigration.briefing.rendershare_cards.create
Docs
docs.search- full-text search over the bundled Speko docs (SDK/adapter
READMEs, hosted llms.txt exports, migration guides). Hits link to spekoai://docs/{slug} resources; spekoai://docs/index lists every doc.
Auth model
The server has no long-lived SpekoAI credential of its own. Tools forward the caller credential to the Speko API. The credential can be an OAuth access token minted by the platform or a Speko API key supplied by the MCP client as Authorization: Bearer ....
If OAuth env vars are configured, /mcp accepts OAuth or Speko API keys. If OAuth env vars are absent, /mcp still requires a valid Speko API key. Partial OAuth configuration fails closed at startup.