Understand the current directory scope
A curated Plugin solves a concrete Harness use case without duplicating this site’s Theme or Full Skin creation role. The authority contains 87 Plugin records: 80 pass publication and seven legacy identities remain in review, on hold, or rejected. Every published Plugin points to its official repository at an immutable revision and records an SPDX license plus curation evidence scoring at least 70.
Browse by the use case you need
| Token | Role | Check |
|---|---|---|
| Discover and start | Find a useful capability and reach a safe first action. | Confirm the entry represents a real Plugin project, not a marketplace or directory, then check installation authority separately. |
| See and understand | Inspect visual, document, or structured information more clearly. | Check data exposure, accessible alternatives, and preview provenance. |
| Remember and retrieve | Keep durable context and bring relevant knowledge back into a task. | Review storage, retention, deletion, and credential boundaries. |
| Research the web | Collect web or browser evidence inside a controlled research workflow. | Review external requests, content trust, citations, and secrets handling. |
| Plan and automate | Turn repeatable work into a visible, controllable workflow. | Verify approvals, side effects, scheduling, cancellation, and rollback. |
| Collaborate and notify | Connect sessions, teammates, or notification channels. | Check recipients, tokens, payload disclosure, and failure behavior. |
| Govern and secure | Inspect policy, configuration, risk, and privileged integration state. | Apply least privilege and verify audit, revocation, and recovery paths. |
| Build and review | Create or inspect code, documents, diagrams, and other work products. | Review writes, generated output, dependencies, tests, and provenance. |
| Measure and optimize | Observe performance, quality, cost, or workflow signals. | Validate metric meaning, sampling, privacy, and optimization tradeoffs. |
| Navigate and focus | Reach the right action or context with less interruption. | Test keyboard, focus, localization, reduced motion, and small screens. |
Read the six-part score before choosing
| Token | Role | Check |
|---|---|---|
| Utility and fit · 25 | Clear value for one or more canonical Harness use cases. | The primary use case must appear in the record and Theme, Skin, marketplace, and directory overlap is excluded. |
| Source and license · 20 | Official immutable repository and reviewed SPDX license evidence. | Open the exact revision and license evidence path; never infer rights from an aggregator row. |
| Security and privacy · 15 | Permissions, network, data, dependency, and execution risk. | Curation is not runtime certification; installation remains closed until independent evidence passes. |
| Maintenance · 15 | Pinned release, update history, ownership, and recovery signals. | Compare the scored evidence with the exact source state instead of repository popularity. |
| Documentation · 15 | Usable setup, behavior, limitation, and recovery guidance. | Verify the instructions belong to the pinned revision and match the represented capability. |
| Differentiation · 10 | A distinct outcome that adds useful choice without duplicating another lane. | Published records need an exact score sum of at least 70 plus concrete item-level evidence. |
Select and recommend with evidence
- 01
Define the interface problem
Describe the user, task, current failure, environment, and measurable improvement before choosing a record.
- 02
Filter by use case and evidence lane
Use the ten use cases, search, capability filters, and distribution state to reduce the set without treating a category as proof.
- 03
Read the complete detail record
Check the immutable source revision, license, asset and trademark disclosures, network behavior, risk disclosure, compatibility state, and rollback note.
- 04
Review the pinned source
Inspect executable code, dependencies, update history, permissions, persistence, and external requests at the exact admitted revision.
- 05
Confirm the fit and open the setup path
Compare the project requirements with your Harness version and workflow, then continue to the pinned source or documented project setup path.
Follow the project setup path
- Open details: compare the preview, workflow tags, compatibility context, and project notes.
- Open the pinned source: read the upstream setup instructions at the exact directory revision.
- Use the project path: follow the upstream release or setup flow that matches your Harness environment.
Evaluate in a controlled workspace
- Use a disposable profile and an isolated environment without production credentials.
- Pin the exact source and dependency graph; record checksums before execution.
- Observe filesystem, process, network, storage, and browser-console behavior.
- Test light, dark, keyboard, reduced-motion, localization, restart, uninstall, and state restoration.
- Publish evidence only after the review policy explicitly admits the result.
Continue exploring
Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
What does this guide verify?
This guide covers: 80 published Plugins from the 87-record audited authority; Ten use cases and ten editorial recommendations ranked from 1 to 10; Official pinned sources, SPDX licenses, and curation scoring
What should I do first?
Start with one of ten use cases, then use the editorial Top 10 as a shortlist that saves comparison time and reduces selection cost. Open a project detail next to verify its official pinned source, SPDX license, score evidence, and runtime boundary.
Which boundary matters most?
The directory is a source-bound shortlist, not a runtime certification. Published, verified, and installable are three separate states. A Plugin stays showcase-only until independent activation, network, uninstall, rollback, and compatibility evidence passes. Images are either official project media or clearly labeled editorial illustrations; editorial illustrations are not runtime screenshots.
Continue learning
Continue from the verified evidence
Compare published artifacts or return to the installation documentation.