albert-maintenance

Maintain and extend the Albert VS Code extension's custom editor providers and host-webview protocols.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/g-akrp/albert --skill albert-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: albert-maintenance
Source: https://github.com/g-akrp/albert/tree/main/.agents/skills/albert-maintenance
Command: npx skills add https://github.com/g-akrp/albert --skill albert-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides specialized guidance for maintaining and extending the Albert VS Code extension, preventing common architectural pitfalls related to its unique host-webview communication model and k6-based execution engine.

Core Features & Use Cases

  • Architectural Guidance: Provides deep insights into the host/webview split, custom editor providers, and the wire-protocol defined in model/types.ts.
  • Development Workflow: Offers standardized procedures for building, type-checking, and packaging the extension, including handling Monaco editor workers and CSP requirements.
  • Use Case: When adding a new feature that requires data exchange between the extension host and a webview, use this skill to ensure the message types are correctly defined and the mutation patterns (mutate vs mutateQuiet) are followed to maintain UI performance.

Quick Start

Use the albert-maintenance skill to guide the implementation of a new field in the request editor while ensuring the host-webview message contract is correctly updated.

Frequently Asked Questions about albert-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up type-safe message passing between a VS Code extension host and a webview?

Type-safe message passing requires defining message types in a shared wire-protocol file and following specific mutation patterns to maintain UI performance during host-webview data exchange.

How does Monaco editor worker loading work with Content Security Policy in a VS Code extension?

Monaco editor worker loading under Content Security Policy requires CSP-compliant configuration to safely execute scripts within the webview while maintaining the extension host security boundaries.

What is the best way to structure API testing infrastructure using k6 in a VS Code extension?

Structuring k6-based API testing infrastructure involves integrating the execution engine within the extension architecture, managing custom editor providers, and validating JSON-based file formats for test definitions.

Why does my webview state management cause UI performance issues when updating the extension host?

Webview state management UI performance issues typically arise from incorrect mutation pattern usage, where distinguishing between standard and quiet mutations prevents unnecessary state broadcast cycles.

Can I use custom editor providers to handle JSON-based file format validation in VS Code extensions?

Custom editor providers support JSON-based file format validation by implementing consistent validation logic within the editor provider, ensuring data integrity across host-webview communication protocols.

What are the limitations when extending a VS Code extension with a custom host-webview communication protocol?

Extending custom host-webview communication protocols requires strict adherence to the defined wire-protocol types and CSP restrictions, limiting arbitrary data exchange and dynamic script execution within webviews.