Individual skill

goal

Set an explicit objective, success criteria, and stopping conditions for the current OpenScience session.

backend/cli/skills/other/goal/SKILL.md

Read pinned source

Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 4,352
Repository last updated: Nov 6, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent Repository topic
ai Repository topic
bun Repository topic
cli Repository topic
llm Repository topic
ml Repository topic
open-source Repository topic
research Repository topic
science Repository topic
ai-agent Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,622 bytes
agents/openai.yamlasset · 172 bytes

Read excerpt


# Goal

Use this skill when the user invokes `/goal` or asks OpenScience to work toward a concrete outcome over multiple turns.

## Contract

Establish the session goal as a compact completion contract:

- Objective: the specific outcome the user wants.
- Success criteria: the checks that prove the outcome is reached.
- Constraints: files, branches, budgets, tools, credentials, publishing rules, or safety limits the user names.
- Stop conditions: complete, blocked, cancelled, budget exhausted, or superseded by a newer user instruction.

If the user provided enough detail, proceed without another question. Ask only when the missing detail would make the work unsafe, irreversible, or impossible to verify.