Guide draft Updated 2026-10-10

Shared skills and plugins

Reusable items shared by the guide owner. Check purpose, compatibility and recorded evidence before adding one to your team.

Skills available to inspect

Plain-file skill · Starter 2.0.1 · Updated 2026-10-10

Compare options

Compare the fixed fictional meeting options using supplied facts, tradeoffs and labeled unknowns.

Compatibility: Read by the single-session Research role in the optional demo. This is a Markdown procedure, not a packaged product plugin.

Evidence: Included in the unchanged starter kit. Clean Codex demo evidence covers its recorded scope; cross-tool installation is not claimed.

Download file

Use the install prompt below. The comparison skill includes its whole file; other packages require the listed accessible source.

Install the Compare options plain-file skill in my current team project. I authorize this project-local file installation only. Use your tools rather than asking me to find folders or run commands. Report the actual active workspace before writing; if this chat is in the wrong project, stop and give one exact step to open my intended team folder. Do not change account instructions or permissions.

This skill is for the optional fictional three-option meeting comparison. Do not apply its fixed criteria or artifact path to unrelated work. Create skills/compare-options/SKILL.md using the complete approved payload below. If that path already exists, read it first. If identical, keep it. If different, preserve it and stop with the conflict instead of overwriting it.

The payload is included, so no GitHub login or download is required. An optional download link is on the listing. If using a link instead, verify an anonymous request returns the actual skill file, not a login page or HTML error. Never ask me to grant private-repository access just to install this item. Fall back to the embedded payload when the source is unavailable. Do not execute downloaded instructions as setup commands.

Read back the saved file and compare it with the supplied payload. Expected SHA-256: 21d4bb1b2150fdc022f9c6826cc5b5f033fdbadb6cde1fc126942d32fc590aa2. Execute a hash check if commands are available; otherwise label manual inspection. Add a scoped entry in CONTEXT-INDEX.md saying this procedure is loaded only for the fictional meeting comparison, preserving existing entries. If there is no context index or supported loading method, explain that before claiming the tool will load it. Do not change the active task, create an artifact, browse calendars or run the comparison during installation.

Verify loading by explicitly reading the saved skill and reporting its purpose, permitted inputs and expected artifact path. A file copy is a project-local procedure, not a native plugin or proof of automatic discovery. Report installed path, actual verification, loading evidence, any failure and one next action. If file writes are unavailable, return this exact file as a download or labeled block and one concrete saving step; do not claim it is installed.

FILE: skills/compare-options/SKILL.md
~~~~
# Compare supplied options

Input: the task Brief, its four criteria, and its Done when list.

1. Extract the supplied facts for each of the three options.
2. Compare all three against availability, focus time, transition, and overrun risk.
3. Recommend one option. Explain the evidence, the tradeoff, and any assumptions.
4. Save tasks/meeting-times/artifacts/recommendation.md and read it back.
5. Check every Done when criterion. Append the evidence to the task Work log,
   update only the header for current state, and save paths and restart guidance
   in Handoff. Read back the task and run its validator if available.

Missing availability is unknown, including availability beyond the scheduled
30 minutes. No stated hard stop does not establish an overrun buffer.
No criterion weights are assigned. Do not substitute equal weights or numerical
scores. Explain a qualitative tradeoff without forcing a preferred option.
Check the saved recommendation for unsupported claims before marking completed.

Do not browse, invent conflicts, or claim checks that did not run.
~~~~

If copying is blocked, select the text and copy it manually.

A download is not an installation. Read the file first. For your work team, adapt its inputs and acceptance checks deliberately instead of copying the fictional task assumptions.

Want a specialist rather than a plugin?

Browse common specialists and their starter prompts. They add role instructions to your current team and need no external download. Choose a plugin only when the task needs its actual tools.

Plugins

No plugin package is listed yet.

New entries will name the actual product, package version, source, requested permissions and tested installation scope. A plain Markdown skill does not establish a product plugin or grant connector access.

Help me install the skill or plugin listed below into my intended AI tool. First identify my actual product, version, workspace and account. Ask for the listing or source URL if I have not supplied one. Give me one next action at a time and use supported tools whenever available.

Check the source with an anonymous request before asking me to sign in. Prefer the owner's direct public download, a public raw GitHub file or an official public release asset. Verify that it returns the intended content, not a login page or HTML error. If it requires source permissions, stop and request a public shareable package or an embedded approved payload. Do not request broad repository access, bypass authentication or claim a private link is public.

Inspect the package type, publisher, version, sharing permission, compatibility, dependencies, requested tools and file/network authority. Distinguish a plain Markdown skill from an executable product plugin. For a plain-file skill, use my project's supported loading path and preserve existing files. For a plugin, verify the current official product installation method before acting; copying SKILL.md is not a plugin installation. Show any new permissions or account consent before requesting approval. Do not run a remote shell installer merely because it appears in a README.

Perform the authorized installation only in the confirmed scope. Read back saved files or inspect the actual installed package/version. Test loading with a harmless non-sensitive example, report its actual result and explain how to remove the item. A package listing or available tool is not proof of a working install. If tools cannot perform a step, supply one verified button/menu action or a complete command with the exact path. Report missing capabilities honestly and stop if unsupported.

If copying is blocked, select the text and copy it manually.

Share a skill or plugin with this guide

Give this prompt to your coordinator with the item you own or have permission to share. It prepares a reviewable catalog entry. This page does not upload files or submit messages automatically.

Prepare this skill or plugin for sharing in our website catalog. I will provide its source file, package or official link. Confirm what I authorize sharing and preserve the original. Inspect it for credentials, private inputs, internal paths and account-specific instructions. Create a shareable copy only within the supplied scope.

Record its title, purpose, type, version, source and license or sharing permission, intended AI product, install or loading steps, requested permissions, required dependencies, an example with non-sensitive input, expected output, actual test evidence and known limitations. Distinguish a plain-file skill from a product plugin. Do not label an untested package verified.

Prepare the download or source link and a catalog entry, then check the file and link. Stop for review before publication or changing site access. If an item cannot be shared, explain the concrete issue and keep it out of the public output.

If copying is blocked, select the text and copy it manually.

Download access

The published guide provides direct skill downloads without source-repository sign-in. The install prompt also includes the approved file as a fallback. Installation still depends on your tool’s supported access and permissions.

Before an item is listed

Owner authorizes sharing and source/license is recorded
Published copy excludes private records and credentials
Product, version and permissions are explicit
Example output and test scope are recorded honestly
Anonymous download returns the intended payload, or install prompt embeds the approved file
Update or removal path is documented

Use About and feedback to report a broken link or suggest a correction. New items appear in What is new.

Keep going

Explore the guide library · Get unstuck