Marketplace concept
A browser skill marketplace lets users install small, inspectable capability packages: a summarizer, a writing-style adapter, a code-review model, a form assistant, or a domain glossary. The package is not trusted merely because it exists. It declares a contract, local permissions, provenance, and evidence.
Package installation flow
| Stage | User-visible evidence |
|---|---|
| Discovery | Skill description and supported base family. |
| Compatibility | Runtime says whether it can run locally. |
| Permission | Package lists file, network, storage, and tool needs. |
| Evaluation | Benchmarks and known fit. |
| Activation | User chooses when it can run. |
FUNCTION install_browser_skill(package, runtime)
show_contract_to_user(package.contract)
REQUIRE runtime.supports(package.base_family)
REQUIRE user_approves(package.permissions)
REQUIRE verify_package_hash(package)
runtime.cache(package)
RETURN activate_for_declared_tasks(package)
END FUNCTIONPositive outcome
Users get local, modular capability without giving every package unlimited power. Good skill packages become reusable assets.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.
Browser and edge runtimeTeleodynamic Architecture and Rust-Native Browser Execution for Modular Tiny Language ModelsEmerging implementation architecture · 52.8 KB
Browser and edge runtimeTeleodynamic AI, Skill Modules, and Rust/WASM Browser ExecutionEmerging implementation architecture · 47.3 KB
Model merging and adaptersTiny-LLM Adapters and LoRA: Breeding Operators, Compatibility, Evaluation, and PromotionEmerging implementation practice · 15.3 KB