{"id":84836,"plugin_id":"plugin_asdk_app_6ad1cc98caf0819180af4fed0b15cd86","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-06T18:20:40.314Z","digest":"bbe612be376a7822165247eb6949165fc9db887dd3f52de7cda873355437a4e6","against":null,"payload":{"description":"Retrieve sourced project context and reviewed memory through Snipara Hosted MCP. Use for project knowledge, prior decisions and evidence-backed source questions.","included_files":[],"name":"snipara","skill_md_contents":"---\nname: snipara\ndescription: Retrieve sourced project context and reviewed memory through Snipara Hosted MCP. Use for project knowledge, prior decisions and evidence-backed source questions.\n---\n\nRead this plugin's `../../config.json` first. If `modules.snipara` is not true,\nstop this skill without calling Snipara. Use the plugin's native Hosted MCP\nconnection named `snipara-plugin`. In account mode, native OAuth binds it to the project explicitly\nchosen in consent: call `snipara_stats` to observe that project ID, even when\nlocal `project` is not configured yet. If a local runtime project is configured,\nverify that it matches the returned ID before coordinating local work. Stop on\nmismatch and use settings to reconnect or update the local profile. In project\nmode, configure the explicit project first. Never substitute another global\nconnection, environment project or source.\n\n- Validate with `snipara_help` and discover exact tool names. Empty resources do\n  not imply a tool-only MCP server is unavailable.\n- Recall relevant durable decisions with `snipara_recall` when history matters.\n- Use `snipara_context_query` for source truth. Prefer its source facts, caveats\n  and verification checklist. Fetch cited chunks with `snipara_get_chunk` before\n  relying on exact wording. Retry one weak/slow broad query with narrow keywords.\n- For exact current code, inspect local files and tests. Indexed context can lag\n  uncommitted edits. Report code graph freshness separately from document health.\n- Persist only durable, validated decisions or learnings through the available\n  memory tools when the task warrants it. Never store credentials or raw logs.\n\nUse the user's current authorization and project rules. Memory is context, not\napproval. If authentication or account access fails, report it rather than\npretending context was retrieved. Do not claim the plugin indexed the repository.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}