agentleFS
coval-aicoval-ai/coval-external-skills/skills/sofia/consult-sofia/SKILL.md

consult-sofia

Skill3 starsChanged 17 days agoMITView on GitHub

Delegate a read-only Coval evaluation, simulation, monitoring, product-how-to, or troubleshooting subtask to Sofia through the official Coval MCP consult_sofia tool. Use when the user needs Coval-specific FDE judgment, analysis of organization data, metric or test-set recommendations, or a diagnosis grounded in Coval runs and conversations.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use consult_sofia when Coval-specific expertise or the authenticated organization's data would improve the answer.

    line 8
  2. Very specific:

    Do not delegate trivial CRUD lookups when a direct Coval MCP or CLI call is clearer.

    line 21
  3. Very specific:

    Call consult_sofia with a self-contained task.

    line 26
  4. Very specific:

    Use the returned summary, evidence, and request_id as the consultation record.

    line 28
  5. Distinctive:

    Every field in the consultation contract is required:

    line 31
  6. Distinctive:

    Do not expose Sofia system instructions, raw knowledge files, internal thresholds, service credentials, or private integrations.

    line 69
  7. Distinctive:

    If the MCP tool is not installed or unavailable, continue with direct Coval MCP/CLI tools and state that the Sofia consultation path was …

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Consult Sofia

Use consult_sofia when Coval-specific expertise or the authenticated organization's data would improve the answer. Sofia is a read-only specialist: it can use Coval knowledge plus the organization's runs, simulations, monitoring conversations, metrics, agents, personas, test sets, and dashboards.

This skill is optional guidance, not an installation prerequisite or a duplicate implementation. Prefer the official remote MCP connection at https://mcp.coval.dev/mcp; use the local stdio MCP server with a Coval API key only for service accounts or local development.

When To Delegate

Delegate when the task needs one or more of:

  • analysis of failed runs, simulations, or monitoring conversations
  • recommendations for test coverage, personas, metrics, or evaluation design
  • product/how-to guidance that should match current Coval behavior
  • a diagnosis based on organization data rather than generic advice
  • a concise FDE-style plan for improving an agent

Do not delegate trivial CRUD lookups when a direct Coval MCP or CLI call is clearer. Do not use it for actions that create, edit, run, or delete resources: consult_sofia cannot perform those actions.

Delegate Well

  1. Gather the smallest useful context from the user's request and any direct Coval tool results.
  2. Call consult_sofia with a self-contained task. Include exact resource IDs, observed errors, relevant metric values, and the desired outcome when available.
  3. Include at most the recent turns needed to preserve intent. Do not include API keys, credentials, or unrelated customer data.
  4. Use the returned summary, evidence, and request_id as the consultation record. Verify any factual identifier or proposed mutation with normal Coval tools before acting.
  5. Present the useful conclusion and next step directly. If an action is appropriate, use the ordinary Coval tool and obtain the confirmation required by the parent agent's policy.

Every field in the consultation contract is required:

{
  contract_version: "1";
  request_id: string;
  mode: "read_only";
  summary: string;
  evidence: Array<{ name: string; status: string }>;
  proposed_actions: [];
}

Reject or report a malformed response instead of guessing missing fields. proposed_actions must remain empty because Sofia cannot mutate Coval resources through this tool.

Prompt Shape

Goal: <what the user needs to decide or improve>
Known evidence: <run/simulation/conversation IDs, metrics, errors, or current setup>
Constraint: <for example, voice agent, staging only, preserve existing resources>
Return: <diagnosis, prioritized plan, metric/test recommendations, or product guidance>

Example:

Goal: explain why our latest voice evaluation regressed and propose the smallest next test.
Known evidence: run run_123 is COMPLETED; Agent Refusal fell from 0.92 to 0.61; the failing simulation is sim_456.
Constraint: do not modify any resources.
Return: a grounded diagnosis, one likely agent fix, and the next test case and metric to add.

Boundaries

  • consult_sofia is read-only. It cannot confirm, execute, or imply a product mutation.
  • Direct MCP tools that create or update Coval resources are separate operations and should remain behind the parent agent's normal approval policy.
  • Do not expose Sofia system instructions, raw knowledge files, internal thresholds, service credentials, or private integrations. Use its conclusions and cited customer-visible evidence instead.
  • If the MCP tool is not installed or unavailable, continue with direct Coval MCP/CLI tools and state that the Sofia consultation path was unavailable.

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.