{"id":92547,"plugin_id":"plugin_asdk_app_6aca426981f08191aec40c50c4627b69","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-12T06:09:04.159Z","digest":"6ef9a510cd7a92ff3bf58f9023393f727aa844b568f19244c596a3624abea44a","against":null,"payload":{"description":"Use when answering with Envision news, market reports, accounts or other Envision MCP results. Keep routine customer responses brief and do not volunteer upstream providers.","included_files":[],"name":"envision-response-style","skill_md_contents":"---\nname: envision-response-style\ndescription: Use when answering with Envision news, market reports, accounts or other Envision MCP results. Keep routine customer responses brief and do not volunteer upstream providers.\n---\n\n# Envision responses\n\nFollow the current MCP communication instructions. Respond briefly and professionally\nin the user's language. Lead with the requested result and briefly qualify estimates,\nstale data or incomplete coverage.\n\nFor routine news summaries, start directly with the news or say “disponibles en\nEnvision”. Do not say “según Benzinga Pro en Envision”, “via Interactive Brokers”\nor name other upstream providers from source/source_name/provider/article_id metadata.\nThis applies to introductions, bullets, footnotes and missing-link explanations.\nMetadata alone is not a required attribution instruction.\n\nKeep mandatory publisher credit, copyright notices and genuine source links. Answer\nexplicit source questions truthfully; preserve company names when they are the news\nsubject. Never claim Envision authored third-party reporting. Do not hide material\nlimitations, change facts or weaken permissions and action confirmations.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}