Add a Web Preview for Shared Skills Before Installation

Feature Requests
1

Problem

Qoder’s current Skill Sharing flow requires recipients to open a shared Skill link in Qoder and install the Skill before they can conveniently inspect its contents.

A shared link such as:

https://qoder.com/link/qoder-work/skill/install?shareId=...

currently acts primarily as an installation deep link. When opened in a browser, the page only provides options such as “Open in Qoder IDE” or “Download Qoder IDE”.

It does not show basic information about the shared Skill, such as:

  • Skill name

  • Publisher / creator

  • Version

  • Description

  • SKILL.md

  • Included scripts

  • Referenced resources

  • File tree

This creates an unnecessary trust and security problem: users are effectively asked to install an unknown Skill before they can properly inspect what they are installing.

This is especially important for Skills because they may contain not only Markdown instructions, but also scripts, references, external commands, or other executable resources.

There is also a UX inconsistency here: Marketplace-style installation flows allow users to inspect an item before installing it, while direct Skill Sharing links currently do not provide an equivalent review step.

Proposed Solution

Turn shared Skill links into lightweight web preview pages instead of install-only redirect pages.

For example:

Shared Skill

Name: example-skill
Publisher: user-name
Version: 1.0.0

Description
...

Files
├── SKILL.md
├── scripts/
│   └── example.py
└── references/
    └── guide.md

[Preview SKILL.md]
[Browse Files]

[Open in Qoder]
[Install Skill]

At minimum, the web page should display:

  1. Skill name

  2. Creator / publisher

  3. Version

  4. Description

  5. Rendered SKILL.md

  6. A list of bundled files

Ideally, users should also be able to inspect the full contents of text-based files and scripts before installation.

The existing Open in Qoder / Install action can remain unchanged.

Why This Matters

1. Security

Users should be able to review instructions and executable content before importing third-party Skills.

The safer workflow is:

Receive Skill link
→ Inspect contents
→ Decide whether it is trustworthy
→ Install

rather than:

Receive Skill link
→ Install
→ Inspect contents afterward

2. Discoverability

A recipient may simply want to understand what a Skill does before deciding whether it is useful.

Opening an IDE and installing something just to read its contents adds unnecessary friction.

3. Better Skill Sharing

A share link should function as an actual representation of the Skill being shared, not merely as an installation command.

This would make Qoder Skill links much easier to share in:

  • GitHub issues and pull requests

  • Team chats

  • Documentation

  • Blog posts

  • Forums

  • Skill collections

  • Internal engineering knowledge bases

4. Consistency

Qoder already encourages users to inspect extensions, Skills, scripts, and related resources before trusting them. Providing a browser preview for shared Skills would make the Skill Sharing workflow consistent with that security model.

Use Case

Someone sends me a Qoder Skill share link.

I do not know what the Skill contains yet.

I would like to open the link in my browser, read its SKILL.md, inspect any scripts it bundles, and then decide whether I want to install it.

Currently I have to install the Skill locally first just to perform that review.

Suggested Priority

:yellow_circle: Medium — Important improvement

It does not block Skill installation, but it significantly improves the security, transparency, and usability of Skill Sharing.

Additional Suggestion

If exposing every bundled file publicly is undesirable, Qoder could still provide a minimum preview consisting of:

  • metadata

  • rendered SKILL.md

  • file names

  • hashes / checksums for bundled files

and require the user to explicitly expand scripts or other files.

An optional warning could also be shown when a Skill includes executable scripts or external commands.