Plan a change you can demonstrate
Explore the Verified change skill through an ordering example.
Open this resource →Reviewed resource examples
Choose guidance for a specific piece of work.
Understand four catalog resources through original explanations, practical assignments, and adoption checks.
A resource should earn its place in the team’s setup. Read what it contributes before selecting its reviewed version.
01 / Reviewed resource examples
Explore four different jobs
Write a result another person can use
Explore the Delivery evidence reference through a release handover.
Open this resource →Investigate a proposed patch
Explore Evidence-based PR review through pagination behavior.
Open this resource →Carry customer scope through a service
Explore Backend boundary guidance through background processing.
Open this resource →02 / Reviewed resource examples
What these public explanations contain
Each page explains a real Betterloop catalog entry through a fictional task. The page is editorial guidance, not the installed resource file.
The four entries shown here have version 1.0.0 and declare Claude Code and Codex support. Other catalog entries can have different requirements.
Resource type matters. A skill guides a task, a workflow organizes a process, a reference supports decisions, and an advisory rule directs attention.
Those forms do not independently grant tool permissions. Read the resource's purpose alongside its dependencies, declared clients, and required organization configuration.
The public pages explain selection inputs and evaluation methods. They do not establish that your company has selected, released, or installed an entry.
Use the task example to judge relevance. Then inspect the exact content your company proposes to adopt through its configuration review process.
03 / Reviewed resource examples
Select for the uncertainty in front of you
Verified change is useful when an implementation needs explicit acceptance conditions and evidence. It helps connect the request with the final demonstrated result.
Delivery evidence supports the handover after work. It helps the agent explain what exists, what was checked, and which delivery state is established.
Evidence-based PR review supports investigation of a proposed patch. It emphasizes affected behavior and concrete findings rather than a target number of comments.
Backend boundary guidance directs attention to trusted context across service operations. It remains advice; the application must implement its authorization and data boundaries.
Some tasks benefit from more than one entry. Keep their roles distinct so reviewers can explain why each selected resource belongs in the configuration.
04 / Reviewed resource examples
Evaluate an entry before team adoption
- 01
Identify the task
Name the observable work the resource should improve.
- 02
Read the selected files
Inspect the exact version and every declared dependency.
- 03
Review the requirements
Check supported clients and any required organization configuration.
- 04
Prepare the configuration change
Include the selected files in the ordinary company review workflow.
- 05
Observe a small trial
Examine retrieval and task behavior separately after release.
- 06
Record the decision
Keep the useful result and unresolved questions with the selected revision.
05 / Reviewed resource examples
Use the local library for supported selection
The connected-device library opens a short-lived read-only browser view. Developers can inspect approved instructions and prepare commands for their selected agents.
The browser itself does not install code. Installation uses the supported command prepared for the chosen resource and clients.
Approved dependencies remain pinned. An update requires an explicit action instead of silently following a mutable latest link.
Native trust, authentication, and tool discovery remain separate from resource selection. Check those requirements when the instructions are available but an integration is not.
Personal resources can remain discoverable. Company approval does not exclude every unmanaged local skill from the native agent's environment.
For actual installation and recovery, follow the developer documentation. A public catalog identifier alone is insufficient grounds for inventing a setup command.