{"id":92786,"plugin_id":"plugin_asdk_app_6a32e6bb349c8191858ce2ca77104214","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-12T12:08:32.542Z","digest":"52354525900051fbe3d36802b12848bf9d5d6b3d8a868b583f5ce3e576c5a328","against":null,"payload":{"description":"Prepare and analyze Dayalogs data through the Dayalogs MCP. Use for saved Analyses, frozen Sources, typed Recipes, recodes, derived variables, exclusions, weighting, multiple Results, segment comparisons, or analytical exports. Use response inspection for raw response counts and quality; use report authoring for report layouts and publication.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":592}],"name":"analyze-dayalogs-data","skill_md_contents":"---\nname: analyze-dayalogs-data\ndescription: Prepare and analyze Dayalogs data through the Dayalogs MCP. Use for saved Analyses, frozen Sources, typed Recipes, recodes, derived variables, exclusions, weighting, multiple Results, segment comparisons, or analytical exports. Use response inspection for raw response counts and quality; use report authoring for report layouts and publication.\n---\n\n# Analyze Dayalogs Data\n\nTurn an admitted Source into a reproducible Recipe and selected Result without changing collected answers.\n\n## Establish the Source\n\n1. Check the connected account's capabilities and available tools. If Analysis tools are unavailable, report the missing capability; do not simulate a Result or change connections.\n2. Read `survey_authoring_help` at `reporting/workflow/help.md` and `reporting/analysis-projects/help.md`. Fetch `reporting/derived-variables/help.md`, `reporting/weighting/help.md`, or `reporting/data-explorer/help.md` only for the requested operation.\n3. Identify the logical Survey, concrete version scope, complete/partial selection, fields and analysis unit. Inspect `get_survey_dataset_context` and existing Analyses before creating another one.\n4. Reuse the current admitted shared Source when available. `get_survey_dataset` supplies the exact published `source_pin`; create an Analysis with `create_analysis_project` and a fresh UUID `request_id`. Select the returned `source_unit_id` deliberately for linked/repeated data. Respondents and repeated occurrences are different bases.\n5. If no admitted Source exists, read `reporting/raw-datasets/help.md`. Preparation and capture do not grant acquisition. Show the exact frozen selection, price and expiry and obtain explicit approval before confirmation, even for zero-price admission. Continuous acquisition needs separate approval of its bounded terms; never infer it from a request to analyze or top up a wallet.\n\n## Build and inspect the Recipe\n\n1. Read `get_analysis_project` and its current draft revision. Save with `save_analysis_recipe`, the observed `expected_revision_id`, and a fresh request UUID. Use either the supported typed flow or the legacy recipe shape from current help, never a mixture.\n2. Preserve field identifiers, codebooks, multiple-answer arrays, missing/unavailable states and source snapshots. Add explicit recodes, derived variables, exclusions and weights; never overwrite original answers or silently convert missing values to zero. Keep one weighting step per Result path.\n3. Use `preview_analysis_project` for the exact saved revision and chosen terminal Result. Its first 20 source rows are a sample, not a full-population calculation.\n4. Explain the proposed changes. Only after explicit approval, call `apply_analysis_project` with `confirm_apply=true`, the current expected revision and a fresh UUID. Continue `calculate_analysis_project` for that returned generation in bounded steps until complete. Preserve the previous published Result while a build is incomplete.\n5. Select the exact published terminal Result, including when a Recipe has several outputs. Read rows with `get_analysis_result_rows`; use `explore_analysis_result` for full-Result distributions, summaries and comparisons. Keep the returned rows pin so subsequent reads use the same generation.\n\n## Deliver the result\n\nState the Source pin, Recipe revision, Result, unit, filters, weighted totals and unweighted bases. Distinguish observed differences from causal claims. Route analytical files through `reporting/exports/help.md`; use `get_analysis_project_reports` to obtain the exact `dataset_source` for a requested Report connection.\n\nOn a revision conflict, stop and reconcile the returned state; do not silently replace guards. Retry unknown mutation outcomes with the identical request id and payload. Source refresh, automatic feeding, Apply, Report publication, paid export and email delivery are separate actions. Never bypass an active continuous-process protection.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}