Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes.
Install Investigate Contract
$ npx skills add ossappscollective/oss-weather --skill investigate-contract -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ossappscollective/oss-weather investigate-contract --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/investigate-contract .claude/skills/investigate-contract && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "investigate-contract" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contract into .claude/skills/investigate-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-contract", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contractType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ossappscollective/oss-weather --skill investigate-contract -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ossappscollective/oss-weather investigate-contract --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/investigate-contract .agents/skills/investigate-contract && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigate-contract" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contract into .agents/skills/investigate-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-contract", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ossappscollective/oss-weather --skill investigate-contract -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ossappscollective/oss-weather investigate-contract --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/investigate-contract .cursor/skills/investigate-contract && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "investigate-contract" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contract into .cursor/skills/investigate-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-contract", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ossappscollective/oss-weather.git --path .claude/skills/investigate-contract--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ossappscollective/oss-weather --skill investigate-contract -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ossappscollective/oss-weather investigate-contract --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/investigate-contract .gemini/skills/investigate-contract && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "investigate-contract" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contract into .gemini/skills/investigate-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-contract", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ossappscollective/oss-weather investigate-contractInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ossappscollective/oss-weather --skill investigate-contract -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/investigate-contract .github/skills/investigate-contract && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "investigate-contract" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contract into .github/skills/investigate-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-contract", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ossappscollective/oss-weather --skill investigate-contract -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ossappscollective/oss-weather investigate-contract --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/investigate-contract .opencode/skills/investigate-contract && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "investigate-contract" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/investigate-contract into .opencode/skills/investigate-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-contract", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
investigate-contract- GitHub stars
- 456
- Token cost
- ~803 tokens
- SKILL.md length
- 399 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes.
- Development work in your project
- SKILL.md covers Read-only (enforce yourself), Interactive vs autonomous, Record assumptions instead of… and Review before posting…
- Calls gh
What it does
Investigate Contract is an agent skill from ossappscollective/oss-weather. Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes. Internal helper invoked by the investigate mode of feat / fix — not meant to be run on its own.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: An OSS weather app for iOS/Android. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/investigate-contract”
What it can do on your machine
Read from SKILL.md and the folder at commit ddd6157. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Investigate Contract loads about 803 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 399 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ossappscollective/oss-weather at commit ddd6157, republished under its MIT licence (© ossappscollective). 399 words, ~803 tokens.
Download SKILL.mdSave it as
.claude/skills/investigate-contract/SKILL.md (or your agent's skills folder).- name
- investigate-contract
- description
- Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes. Internal helper invoked by the investigate mode of feat / fix — not meant to be run on its own.
- disable-model-invocation
- true
Applies whenever a skill runs with --investigate. The domain-specific output (a plan, or a bug triage) and any labeling live in the calling skill; this is the shared contract.
Read-only (enforce yourself)
Investigate mode is strictly read-only: never edit code, never create a branch, never commit. Nothing at the tool level blocks you here, so hold the line yourself. The only writes you make are the GitHub-issue comment (gh issue comment, via the save-plan-to-github skill) and, in autonomous mode, a label the calling skill may add (gh issue edit --add-label). Other hard limits (no force-push, no destructive shell) are enforced by .claude/settings.json deny/ask rules — if a tool call is blocked, do not work around it.
Interactive vs autonomous
--investigate is interactive by default; --investigate --auto is autonomous. The analysis is identical — only the human-in-the-loop differs:
Interactive (--investigate) | Autonomous (--investigate --auto) | |
|---|---|---|
| Questions | May ask 1-2 targeted questions when a material ambiguity changes the output | Never ask — record the assumption and proceed |
| Use case | While the user is at their machine | Unattended batch (e.g. nightly) |
Record assumptions instead of blocking
When the issue is underspecified, don't stall. Interactive: ask only the question(s) that materially change the output; for everything minor, state the assumption explicitly in the posted block (under an "Assumptions" heading) and proceed. Autonomous: never ask — always record the assumption and continue. A reader seeing your assumptions is far more useful than a half-done investigation waiting on input.
Show full SKILL.md (162 more words)Show less
Review before posting (interactive only)
The posted block is the deliverable — but in interactive mode the user is sitting with you, so let them shape it before it lands on the issue. Draft the plan, present it in chat, fold in their edits, and post the comment only once they approve. Posting an unreviewed plan and asking for validation after it's already on the issue is backwards when a human is right there to catch a wrong assumption or a missing constraint first.
For the in-chat review, show every section expanded — don't wrap sections in <details> collapsibles (those hide content the user wants to see now). Keep the tables/bullets as-is. Assemble the final comment (with <details> around the long sections) only at the moment you post it, after approval.
Autonomous (--auto) is the exception: there's no human to ask, so post directly — the gh issue comment call is the deliverable and the only write. Never block an unattended run waiting on approval.
© ossappscollective, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/investigate-contract of ossappscollective/oss-weather.
Open the folder on GitHubat commit ddd6157
Compare with similar skills
Investigate Contract next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Investigate Contract this skillossappscollective/oss-weather | 456 | — | ~803 | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from ossappscollective/oss-weather
All 8 skills in this repoCommit
ossappscollective/oss-weather
MANDATORY skill for ALL commits. An agent skill from ossappscollective/oss-weather.
Open PR
ossappscollective/oss-weather
MANDATORY skill for ALL pull requests. An agent skill from ossappscollective/oss-weather.
Feat
ossappscollective/oss-weather
Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with --investigate.
Fix
ossappscollective/oss-weather
Debug and fix any non-trivial issue end-to-end, OR triage a GitHub bug issue read-only.
Understand Project
ossappscollective/oss-weather
Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface.
Branch Check
ossappscollective/oss-weather
Ensure you're on a correct working branch off up-to-date main before planning or editing — starting from a GitHub issue when one is in play.
Related
Categories
Questions about Investigate Contract
What does Investigate Contract do?
Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes. Investigate Contract is an agent skill from ossappscollective/oss-weather. Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes.
When should I use Investigate Contract?
Investigate Contract fits situations like: development work in your project.
How do I install Investigate Contract in Claude Code?
Run `npx skills add ossappscollective/oss-weather --skill investigate-contract -a claude-code`. Or copy the skill folder (.claude/skills/investigate-contract in ossappscollective/oss-weather) into .claude/skills/investigate-contract in your project. Claude Code loads it when a task matches its description.
How do I install Investigate Contract in Codex?
Run `npx skills add ossappscollective/oss-weather --skill investigate-contract -a codex`. Or copy the skill folder (.claude/skills/investigate-contract in ossappscollective/oss-weather) into .agents/skills/investigate-contract in your project. Codex loads it when a task matches its description.
Can I use Investigate Contract in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ossappscollective/oss-weather --skill investigate-contract -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigate-contract, .gemini/skills/investigate-contract, .github/skills/investigate-contract and .opencode/skills/investigate-contract in your project.
What does Investigate Contract need to run?
Going by SKILL.md and its folder, Investigate Contract needs the command-line tools its instructions call (gh).
Does Investigate Contract access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Investigate Contract safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Investigate Contract use?
Investigate Contract is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Investigate Contract use?
About 803 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Investigate Contract?
Skills that share tags, products or a category with Investigate Contract: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigate Contract?
ossappscollective (a GitHub organization) maintains it in ossappscollective/oss-weather, which has 456 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.
Source: ossappscollective/oss-weather on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.