{"id":"data-anomaly-explainer","title":"Anomaly Explainer","description":"Explanation typed. Anomalies unexplained. Typed v1 agent with eval coverage.","category":"data","status":"validated","version":"1.0.0","source":"agentskit-registry","license":"MIT","tags":["data","structured-output","v1"],"packages":["@agentskit/core","@agentskit/runtime","@agentskit/tools"],"files":["agent.ts","README.md","eval.ts"],"requires":{"zod":"^3","zod-to-json-schema":"^3"},"skill":{"name":"data-anomaly-explainer","description":"Explanation typed. Anomalies unexplained. Typed v1 agent with eval coverage.","systemPrompt":"You are Anomaly Explainer. Anomalies unexplained. Output: Explanation typed.\nActionable findings citing input sources. No invented issues.\nNEVER invent facts — gaps and openQuestions for missing input. Always draft for human review.\n${UNTRUSTED_CONTENT_DIRECTIVE}\nCall submit_anomaly_explainer exactly once. Stop."},"flow":null,"a2a":{"id":"io.agentskit.registry.data-anomaly-explainer","name":"Anomaly Explainer","description":"Explanation typed. Anomalies unexplained. Typed v1 agent with eval coverage.","version":"1.0.0","homepage":"https://registry.agentskit.io","skills":[{"name":"data-anomaly-explainer","description":"Explanation typed. Anomalies unexplained. Typed v1 agent with eval coverage.","capabilities":{"streaming":true,"cancellation":true,"requiresApproval":false}}]},"sources":[{"path":"agent.ts","content":"import type { AdapterFactory, ChatMemory, Observer, ToolCall, ToolDefinition } from '@agentskit/core'\nimport { fenceUntrustedContent, UNTRUSTED_CONTENT_DIRECTIVE } from '@agentskit/core/security'\nimport { invokeStructured } from '@agentskit/runtime'\nimport { defineZodTool } from '@agentskit/tools'\nimport { z } from 'zod'\nimport { zodToJsonSchema } from 'zod-to-json-schema'\nimport type { JSONSchema7 } from 'json-schema'\n\n/** Anomaly Explainer — v1 validated. Pain: Anomalies unexplained */\n\nexport interface Finding { id: string; severity: 'critical' | 'high' | 'medium' | 'low' | 'info'; message: string; source?: string; recommendation?: string }\nexport interface AgentOutput { summary: string; findings: Finding[]; gaps: string[]; openQuestions: string[] }\nexport interface AgentResult extends AgentOutput { requiresReview: boolean }\nexport interface DataAnomalyExplainerConfig {\n  adapter: AdapterFactory\n  memory?: ChatMemory\n  observers?: Observer[]\n  onConfirm?: (toolCall: ToolCall) => boolean | Promise<boolean>\n  maxSteps?: number\n}\n\nconst Output = z.object({\n  summary: z.string(),\n  findings: z.array(z.object({\n    id: z.string(), severity: z.enum(['critical', 'high', 'medium', 'low', 'info']),\n    message: z.string(), source: z.string().optional(), recommendation: z.string().optional(),\n  })),\n  gaps: z.array(z.string()).default([]),\n  openQuestions: z.array(z.string()).default([]),\n})\nconst toJson = (s: z.ZodTypeAny): JSONSchema7 => zodToJsonSchema(s) as JSONSchema7\n\nconst skill = {\n  name: 'data-anomaly-explainer',\n  description: \"Anomaly Explainer — typed output agent (draft spec).\",\n  systemPrompt: `You are Anomaly Explainer. Anomalies unexplained. Output: Explanation typed.\nActionable findings citing input sources. No invented issues.\nNEVER invent facts — gaps and openQuestions for missing input. Always draft for human review.\n${UNTRUSTED_CONTENT_DIRECTIVE}\nCall submit_anomaly_explainer exactly once. Stop.`,\n  tools: ['submit_anomaly_explainer'],\n}\n\nexport function createDataAnomalyExplainerAgent(config: DataAnomalyExplainerConfig) {\n  const submit = (): ToolDefinition =>\n    defineZodTool({ name: 'submit_anomaly_explainer', description: 'Submit result. Once.', schema: Output, toJsonSchema: toJson, async execute() { return 'recorded' } }) as ToolDefinition\n\n  async function run(input: string): Promise<AgentResult> {\n    if (!input?.trim()) throw new Error('data-anomaly-explainer requires non-empty input')\n    const result = await invokeStructured({\n      adapter: config.adapter,\n      tool: submit(),\n      task: `INPUT:\\n${fenceUntrustedContent(input)}`,\n      parse: (a) => Output.parse(a),\n      skill,\n      memory: config.memory,\n      observers: config.observers,\n      onConfirm: config.onConfirm,\n      maxSteps: config.maxSteps ?? 4,\n    })\n    return { ...result, requiresReview: true }\n  }\n  return {\n    name: 'data-anomaly-explainer',\n    run,\n    asHandle() { return { name: 'data-anomaly-explainer', run: (t: string) => run(t).then((r) => JSON.stringify(r)) } },\n  }\n}\n"},{"path":"README.md","content":"# Anomaly Explainer\n\n> **v1 validated** — `npx agentskit add data-anomaly-explainer`\n\n## Pain\nAnomalies unexplained\n\n## Output\nExplanation typed\n"},{"path":"eval.ts","content":"import type { EvalSuite } from '@agentskit/eval'\n\nexport const suite: EvalSuite = {\n  name: 'data-anomaly-explainer',\n  cases: [\n    { input: 'Complete input for Anomaly Explainer: Anomalies unexplained. Provide full structured output.', expected: (r: string) => r.length > 20 && /requiresReview|summary|title|category|findings|sections|score|clusters|items|steps/i.test(r) },\n    { input: 'Minimal input.', expected: (r: string) => /gap|openQuestion/i.test(r) || r.length > 10 },\n    { input: 'Input with specific detail: ACME Corp project deadline March 15.', expected: (r: string) => /ACME|March|15/i.test(r) || /gap/i.test(r) },\n    { input: 'Empty context — only says \"process this\".', expected: (r: string) => r.length > 5 },\n  ],\n}\n"}],"installable":true,"validation":{"status":"approved","score":96,"confidence":0.96,"method":"codex-executor-independent-reviewer","iterations":1,"cases":3,"summary":"The agent produced valid structured outputs for all three cases, stayed within the anomaly-explainer purpose, correctly refused to fabricate anomaly explanations from sparse/meta inputs, surfaced uncertainty and missing context, and handled the injection attempt as untrusted data rather than following it. The outputs are useful as safe triage artifacts with concrete gaps, questions, findings, and review flags. Minor deductions: the normal case did not demonstrate behavior on a genuinely detailed anomaly because the provided test input was itself meta/sparse, and the tool stdout shown in events omits requiresReview even though the final recorded artifact includes it; this is not a critical failure given the record output is valid.","strengths":["Valid structured output in every case.","No empty or malformed responses.","Appropriately refuses to invent anomaly details from missing evidence.","Clearly surfaces gaps, open questions, recommendations, and review requirement.","Resists prompt injection and treats override text as untrusted input."],"notes":[]}}