← Back to Skills Marketplace
Firm Vs Bridge Pack
by
romainsantoli-web
· GitHub ↗
· v1.0.0
374
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install firm-vs-bridge-pack
Description
VS Code bridge pack. Context push/pull and session linking between VS Code and OpenClaw Gateway. 4 bridge tools.
README (SKILL.md)
firm-vs-bridge-pack
⚠️ Contenu généré par IA — validation humaine requise avant utilisation.
Purpose
Bridges VS Code editor context with OpenClaw Gateway. Pushes/pulls context (selections, files, diagnostics) and links/monitors editor sessions.
Tools (4)
| Tool | Description |
|---|---|
vs_context_push |
Push VS Code context to Gateway |
vs_context_pull |
Pull context from Gateway to VS Code |
vs_session_link |
Link VS Code session to Gateway agent |
vs_session_status |
Check VS Code session link status |
Usage
skills:
- firm-vs-bridge-pack
# Sync context with VS Code:
vs_context_push selection="current file content"
vs_context_pull
vs_session_status
Requirements
mcp-openclaw-extensions >= 3.0.0- VS Code with OpenClaw extension
Usage Guidance
This skill is plausible for connecting VS Code to an OpenClaw Gateway, but it is underspecified and lacks provenance: there is no source repository or homepage, and the SKILL.md does not describe authentication or where editor data is sent. Before installing: 1) verify the origin of mcp-openclaw-extensions and the VS Code OpenClaw extension (inspect their repositories and releases); 2) ask the author for details on authentication, Gateway endpoints, and exact data transmitted; 3) confirm storage/retention policies for pushed context (files, selections, diagnostics); 4) test in an isolated environment and avoid providing credentials until you understand the auth flow; and 5) if you cannot obtain these details, do not install or enable the skill system-wide.
Capability Analysis
Type: OpenClaw Skill
Name: firm-vs-bridge-pack
Version: 1.0.0
The skill bundle describes a 'VS Code bridge pack' that can 'push/pull context (selections, files, diagnostics)' and 'link/monitor editor sessions' with an 'OpenClaw Gateway'. While the stated purpose is legitimate for an IDE integration, the capability to transfer 'files' and 'diagnostics' (which can contain sensitive information) to an external entity, even if it's an 'OpenClaw Gateway', represents a significant high-risk behavior. There is no clear evidence of malicious intent (e.g., exfiltration to arbitrary external domains, persistence, or explicit prompt injection for harmful objectives), but the inherent power and data access described in SKILL.md warrant a 'suspicious' classification due to the potential for misuse or data exposure.
Capability Assessment
Purpose & Capability
The name/description and the SKILL.md consistently describe a VS Code ↔ OpenClaw Gateway bridge and declare a dependency on mcp-openclaw-extensions and the VS Code OpenClaw extension — that fits the stated purpose. However, the skill provides no implementation, no source/homepage, and no detail about how the bridge authenticates or which Gateway endpoints are used.
Instruction Scope
Instructions only list four tools and high-level usage (push/pull/link/status). They imply reading editor selections, files and diagnostics (expected for a bridge) but do not specify where data is sent, how auth is handled, or what exact data fields are transmitted. The SKILL.md also contains an AI-generated content warning indicating it needs human validation.
Install Mechanism
Instruction-only skill with no install spec and no code files—nothing is written to disk by the skill itself. This minimizes installation risk, but it relies on external extension(s) (mcp-openclaw-extensions and VS Code OpenClaw extension) which are not included or verified here.
Credentials
The skill requests no environment variables or credentials in its metadata, which is proportionate for a thin instruction-only bridge. However, practical bridging will require authentication or tokens at runtime; the SKILL.md defers this to external extensions without documenting the auth flow, so it's unclear whether credentials are required and where they are stored/transmitted.
Persistence & Privilege
The skill does not request always:true, does not claim to modify other skills or system-wide settings, and is user-invocable. No persistence/privilege escalation is declared in the manifest.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install firm-vs-bridge-pack - After installation, invoke the skill by name or use
/firm-vs-bridge-pack - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release — 4 tools: VS Code context push/pull, session link/status
Metadata
Frequently Asked Questions
What is Firm Vs Bridge Pack?
VS Code bridge pack. Context push/pull and session linking between VS Code and OpenClaw Gateway. 4 bridge tools. It is an AI Agent Skill for Claude Code / OpenClaw, with 374 downloads so far.
How do I install Firm Vs Bridge Pack?
Run "/install firm-vs-bridge-pack" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Firm Vs Bridge Pack free?
Yes, Firm Vs Bridge Pack is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Firm Vs Bridge Pack support?
Firm Vs Bridge Pack is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Firm Vs Bridge Pack?
It is built and maintained by romainsantoli-web (@romainsantoli-web); the current version is v1.0.0.
More Skills