{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-ms-inkling-ms-inkling","slug":"inkling","name":"Inkling","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=ms-inkling.ms-inkling","page_url":"https://unfragile.ai/inkling","categories":["code-editors"],"tags":["__ext_ink","ai","inkling","reinforcement"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-ms-inkling-ms-inkling__cap_0","uri":"capability://code.generation.editing.inkling.syntax.highlighting.and.semantic.validation","name":"inkling syntax highlighting and semantic validation","description":"Provides real-time syntax coloring and semantic error/warning detection for Inkling domain-specific language files within VS Code. Integrates with VS Code's language server protocol (LSP) or equivalent diagnostic system to parse .inkling files, identify syntax violations, and surface inline diagnostics (squiggly underlines, error messages) without requiring external compilation or manual validation steps.","intents":["I want to write Inkling code with immediate visual feedback on syntax errors","I need to catch Inkling language violations as I type, not after compilation","I want syntax-aware code coloring to distinguish Inkling keywords, identifiers, and literals"],"best_for":["Bonsai platform users developing reinforcement learning simulators in Inkling","Teams migrating legacy Inkling v1 code to v2 syntax","Solo developers prototyping AI training scenarios with Inkling DSL"],"limitations":["Limited to Inkling language only — no cross-language support or polyglot analysis","No project-level or multi-file semantic analysis documented — validation appears file-scoped","Unknown whether partial syntax support exists for edge cases or experimental Inkling features","No IDE refactoring tools (rename, extract, organize imports) mentioned"],"requires":["Visual Studio Code (version requirement unknown, likely 1.50+)",".inkling file extension or explicit language mode selection","Extension installed from VS Code Marketplace (ms-inkling.ms-inkling)"],"input_types":["Inkling source code (.inkling files)","File content in VS Code editor buffer"],"output_types":["Syntax-highlighted code display","Inline diagnostics (errors, warnings) with line/column positions","Diagnostic messages in VS Code Problems panel"],"categories":["code-generation-editing","language-support"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ms-inkling-ms-inkling__cap_1","uri":"capability://code.generation.editing.inkling.v1.to.v2.syntax.conversion.command","name":"inkling v1-to-v2 syntax conversion command","description":"Exposes a VS Code command palette action that transforms Inkling v1 syntax to v2 (or vice versa) by parsing the current file's AST, applying syntax transformation rules, and outputting converted code. The conversion likely handles breaking changes between language versions (e.g., renamed keywords, restructured configuration blocks, updated function signatures) without requiring manual line-by-line rewrites.","intents":["I need to migrate my Inkling v1 simulator code to v2 syntax automatically","I want to understand what changed between Inkling versions by seeing the transformed code","I need to convert a single file or batch of Inkling files to the new language version"],"best_for":["Teams maintaining legacy Inkling v1 simulators and upgrading to v2","Bonsai platform users adopting new language features in v2","Developers automating migration workflows across multiple Inkling projects"],"limitations":["Conversion directionality unknown — may be unidirectional (v1→v2 only) or bidirectional","No batch/multi-file conversion documented — appears to operate on single active file only","Unknown whether conversion handles all v1 features or only common patterns; edge cases may require manual fixes","No preview or diff mode documented — conversion may overwrite original file without undo safety","Conversion logic and transformation rules are not open-source or documented"],"requires":["Active Inkling file open in VS Code editor","File must be valid (or mostly valid) Inkling v1 or v2 syntax","Command palette access (Ctrl+Shift+P / Cmd+Shift+P)","Extension version with conversion command implemented"],"input_types":["Inkling v1 source code (.inkling files)","Inkling v2 source code (.inkling files)"],"output_types":["Converted Inkling v2 source code (or v1, if bidirectional)","Modified file buffer in VS Code editor"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ms-inkling-ms-inkling__cap_2","uri":"capability://code.generation.editing.inkling.language.mode.detection.and.file.association","name":"inkling language mode detection and file association","description":"Automatically detects and registers .inkling file extensions with VS Code's language system, enabling the extension to activate its syntax highlighting and validation features. Uses VS Code's language contribution mechanism to associate the Inkling language identifier with the extension, ensuring that opening any .inkling file triggers the language server and diagnostic pipeline without manual configuration.","intents":["I want .inkling files to automatically use the correct syntax highlighting when I open them","I need VS Code to recognize Inkling as a distinct language, not as plain text or generic code","I want the extension to activate automatically when I work with Inkling files"],"best_for":["Bonsai platform users with existing .inkling file projects","Teams standardizing on .inkling file extension for Inkling code","Developers new to Inkling who expect automatic language detection"],"limitations":["Only recognizes .inkling file extension — no support for alternative extensions or in-file language markers","No manual language mode override documented — users must rely on file extension","Unknown whether extension handles Inkling code embedded in other file types (e.g., .py with Inkling blocks)","File association is global to VS Code — cannot be scoped to specific workspaces or projects"],"requires":["Visual Studio Code with language contribution support","File with .inkling extension in workspace","Extension installed and activated"],"input_types":["File system paths with .inkling extension"],"output_types":["Language mode assignment (Inkling)","Activation of syntax highlighting and validation"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ms-inkling-ms-inkling__cap_3","uri":"capability://code.generation.editing.inline.diagnostic.reporting.for.inkling.errors.and.warnings","name":"inline diagnostic reporting for inkling errors and warnings","description":"Integrates with VS Code's diagnostic API to surface Inkling syntax and semantic errors as inline squiggly underlines, hover tooltips, and entries in the Problems panel. The extension parses Inkling source code, identifies violations against the language grammar and semantic rules, and reports diagnostics with precise line/column positions and actionable error messages, enabling developers to fix issues without leaving the editor.","intents":["I want to see Inkling errors highlighted in red as I type, not after saving or compiling","I need clear error messages that explain what's wrong with my Inkling syntax","I want to navigate to all Inkling errors in my file via the Problems panel"],"best_for":["Inkling developers who prefer real-time feedback during coding","Teams enforcing code quality standards via inline error visibility","Developers unfamiliar with Inkling syntax who benefit from immediate guidance"],"limitations":["Diagnostic scope appears file-local — no cross-file dependency checking or project-level semantic analysis","Unknown whether diagnostics include suggestions or quick-fixes (auto-correction)","Error message clarity and completeness depend on extension's error catalog — edge cases may produce generic messages","No configuration for diagnostic severity levels (e.g., treating warnings as errors) documented","Diagnostic latency unknown — real-time reporting may have perceptible delay on large files"],"requires":["Inkling file open in VS Code editor","Extension activated and language server running","Valid or partially-valid Inkling syntax (parser must not crash on malformed input)"],"input_types":["Inkling source code in editor buffer"],"output_types":["Diagnostic objects with severity (error/warning), message, line/column range","Inline squiggly underlines in editor","Entries in VS Code Problems panel","Hover tooltips with error details"],"categories":["code-generation-editing","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":42,"verified":false,"data_access_risk":"high","permissions":["Visual Studio Code (version requirement unknown, likely 1.50+)",".inkling file extension or explicit language mode selection","Extension installed from VS Code Marketplace (ms-inkling.ms-inkling)","Active Inkling file open in VS Code editor","File must be valid (or mostly valid) Inkling v1 or v2 syntax","Command palette access (Ctrl+Shift+P / Cmd+Shift+P)","Extension version with conversion command implemented","Visual Studio Code with language contribution support","File with .inkling extension in workspace","Extension installed and activated"],"failure_modes":["Limited to Inkling language only — no cross-language support or polyglot analysis","No project-level or multi-file semantic analysis documented — validation appears file-scoped","Unknown whether partial syntax support exists for edge cases or experimental Inkling features","No IDE refactoring tools (rename, extract, organize imports) mentioned","Conversion directionality unknown — may be unidirectional (v1→v2 only) or bidirectional","No batch/multi-file conversion documented — appears to operate on single active file only","Unknown whether conversion handles all v1 features or only common patterns; edge cases may require manual fixes","No preview or diff mode documented — conversion may overwrite original file without undo safety","Conversion logic and transformation rules are not open-source or documented","Only recognizes .inkling file extension — no support for alternative extensions or in-file language markers","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.73,"quality":0.18,"ecosystem":0.27,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.803Z","last_scraped_at":"2026-05-03T15:20:29.937Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=inkling","compare_url":"https://unfragile.ai/compare?artifact=inkling"}},"signature":"RAwI/s/kiqjvd+RakNIBwKH3DVqY5/KbEaN0P58OvOvdOiy9oRsyGtT+fscuSRE+Mgs5IpbyEpsyNUFVceHhBA==","signedAt":"2026-06-23T12:35:29.279Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/inkling","artifact":"https://unfragile.ai/inkling","verify":"https://unfragile.ai/api/v1/verify?slug=inkling","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}