Flights
asgeirtj/system_prompts_leaks
Research, book, or manage flights, including check-in. An agent skill from asgeirtj/system_prompts_leaks.
Navigate problems along lines of flight by composing operations from arbitrary domains.
$ npx skills add LeoYeAI/openclaw-master-skills --skill flight-lines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills flight-lines --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/flight-lines .claude/skills/flight-lines && 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 "flight-lines" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-lines into .claude/skills/flight-lines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flight-lines", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-linesType 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 LeoYeAI/openclaw-master-skills --skill flight-lines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills flight-lines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/flight-lines .agents/skills/flight-lines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flight-lines" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-lines into .agents/skills/flight-lines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flight-lines", 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 LeoYeAI/openclaw-master-skills --skill flight-lines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills flight-lines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/flight-lines .cursor/skills/flight-lines && 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 "flight-lines" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-lines into .cursor/skills/flight-lines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flight-lines", 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/LeoYeAI/openclaw-master-skills.git --path skills/flight-lines--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 LeoYeAI/openclaw-master-skills --skill flight-lines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills flight-lines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/flight-lines .gemini/skills/flight-lines && 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 "flight-lines" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-lines into .gemini/skills/flight-lines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flight-lines", 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 LeoYeAI/openclaw-master-skills flight-linesInstalls 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 LeoYeAI/openclaw-master-skills --skill flight-lines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/flight-lines .github/skills/flight-lines && 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 "flight-lines" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-lines into .github/skills/flight-lines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flight-lines", 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 LeoYeAI/openclaw-master-skills --skill flight-lines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills flight-lines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/flight-lines .opencode/skills/flight-lines && 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 "flight-lines" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/flight-lines into .opencode/skills/flight-lines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flight-lines", 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.
flight-linesNavigate problems along lines of flight by composing operations from arbitrary domains.
Flight Lines is an agent skill from LeoYeAI/openclaw-master-skills. Navigate problems along lines of flight by composing operations from arbitrary domains. Operations are deterritorialized capacities—they don't belong to their origin domains. Mycorrhizal signaling + ham radio protocols + rare book dealer networks can compose into a single assemblage. The composer maintains parallel work-paths, constantly revising as new structure emerges.
Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Flight Lines loads about 4.9k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 2,493 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.
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.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 2,493 words, ~4,924 tokens.
.claude/skills/flight-lines/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Knowledge gets organized into domains—epidemiology, jazz theory, mycology, contract law. These are stratifications: useful for organizing expertise but not fundamental boundaries. They're territories.
Operations exist beneath these strata. "Sentinel surveillance" isn't essentially about disease—it's a capacity: strategic monitoring of high-signal locations in sparse search spaces. "Reharmonization" isn't essentially about jazz—it's changing underlying structure while preserving surface continuity. Operations are deterritorialized capacities that got captured by domain-strata through historical accident.
The conventional approach to problems stays within domain boundaries. Dating advice for dating problems. Language pedagogy for language problems. This is navigating along the strata—safe, predictable, limited.
Lines of flight are movements that escape stratified territories. When you recognize that rare book dealer "want list circulation" addresses the same structural constraint as epidemiological "contact tracing"—and both could apply to finding collaborators in a new city—you're accessing operations on a plane of consistency where domain labels don't constrain what composes with what.
Key insight: Operations compose based on structural fit, not semantic coherence. An assemblage of mycorrhizal networks + ham radio + rare book collecting is domain-incoherent but can be structurally coherent for a given problem.
Stratified approach:
Compositional approach:
A specific capacity with defined mechanics—not a concept or metaphor:
Examples:
A property of the problem that creates difficulty—independent of domain framing:
A composition of heterogeneous operations that work together. Assemblages don't require domain coherence—they require structural coherence:
A trajectory that escapes stratified solutions. When standard approaches feel exhausted and you start pulling operations from mycology and espionage and thermodynamics to address your problem—you're following a line of flight.
Not all lines of flight succeed. Some dissipate, some get recaptured by strata, some open genuine new territory.
This is not a linear pipeline. It's an ongoing process with parallel paths and constant revision.
Don't ask "what kind of problem is this?" (that's seeking a stratum to navigate within).
Ask: "What are the parallel concerns here? What structural properties make each one hard?"
Example: Fresh Start in a New City
An adult has moved to a new city. They want to build a life—not just survive, but flourish. Not replicate their old life, but become someone new while honoring who they've been.
Parallel concerns identified:
For each concern, structural constraints:
Territory constraints:
Connection constraints:
Becoming constraints:
For each structural constraint, ask: "What operations address this structural property?"
Don't constrain by domain. Query across everything you understand.
Cold start constraint (no existing network):
Operations that address cold start:
Sparse matching constraint (most people aren't compatible):
Operations:
Identity flux constraint (old identity doesn't fit):
Operations:
Don't create one master plan. Open multiple lines simultaneously.
Line A: Territorial Establishment
Line B: Network Seeding
Line C: Becoming Work
Run operations. Generate concrete outputs:
CQ calls executed:
Sentinel surveillance executed:
Want list circulation executed:
Nurse log executed:
Here's where the composer aspect becomes dynamic.
Execution changes structure. New structure reveals new constraints. New constraints suggest new operations.
After two weeks:
What emerged:
New constraints revealed:
New operations pulled in:
Revised assemblage:
The process continues until:
The composer doesn't have an end state. It's a way of navigating.
"Sentinel surveillance" works whether tracking disease, monitoring rare species, or finding your people in a new city. The operation exists independent of its origin domain.
When you use an operation, you're not doing "epidemiology" in your social life. You're accessing a capacity that epidemiology happened to articulate.
Mycorrhizal networks + ham radio + rare books is semantically absurd. It can be structurally coherent.
Domain mixing isn't a clever trick—it's the natural result of accessing operations beneath their domain-strata.
Don't create a master plan and execute it. Open multiple lines. Let some intensify, let some dissipate. Revise as structure changes.
The composer is an ongoing process, not a one-shot planner.
You can't fully analyze a problem then solve it. Execution reveals constraints analysis missed. Operations produce structure that suggests new operations.
Think: probe, act, sense, respond. Not: analyze, plan, execute.
The output of one operation becomes input for selecting the next. "Want list circulation" might surface someone who teaches you about "guild structures" (medieval crafts), which becomes a new operation addressing constraints you hadn't seen.
Domains you didn't know could contribute get pulled in as you go.
If you can generate concrete outputs—specific actions, real artifacts, actual protocols—the composition is working.
Vague analogies ("my social life is like a mycelial network") aren't operations. Specific procedures ("broadcast specific criteria through existing contacts, let matches come to you") are.
Use when:
Don't use when:
Open multiple lines. Most won't go anywhere. A few will resonate. Intensify those, let others go dormant or dissipate.
Don't pick one approach and commit. Don't try to optimize everything simultaneously.
Success with one operation often reveals related ones:
Let working operations pull in their neighbors.
When an operation doesn't quite fit, the friction reveals constraints you missed.
"Stepping stones assumes fixed patches, but my safe spaces are temporally unstable" → Reveals temporal dynamics constraint you hadn't modeled.
Breakdowns are information, not failures.
Not every line of flight needs to stay deterritorialized. Sometimes you find a new stratum that actually works. A stable job, a solid friend group, a neighborhood that fits.
The goal isn't permanent deterritorialization. It's having the capacity to follow lines of flight when strata aren't working.
If your assemblage composes 4+ unrelated domains, you're probably generating novel approaches.
Homogeneous composition (all operations from one domain) suggests staying within conventional territory. That's fine when it works.
Month 1: Opening Lines
Territory line: Found temporary housing, started sentinel surveillance on neighborhoods Connection line: CQ calls across three contexts, want list to five people Becoming line: Nurse log inventory (what from past is substrate?)
Concrete outputs:
Month 2: Selective Intensification
What emerged:
Revised assemblage:
Month 3: Structure Stabilizes and Transforms
Territory: Found housing in target neighborhood. Territorial concern moves to background. Connection: Three genuine connections forming. Network has seed structure. Becoming: Clearer sense of new version. Some branches merged back, some still open.
New concerns emerging:
New operations being queried:
The problem has transformed. You're no longer "starting fresh"—you're in the next phase. The composer continues.
vs. Self-help / Life coaching: Self-help stays within its stratum. "Network more." "Put yourself out there." Flight lines pull operations from mycology and ham radio and epidemiology.
vs. Analogical reasoning: Analogies map concepts. "My social life is like a garden." Flight lines execute operations. "Apply succession dynamics: pioneer species first, then guilds."
vs. Design thinking: Design thinking iterates within problem domain. Flight lines compose across domains based on structural fit.
vs. Systems thinking: Systems thinking analyzes dynamics within a frame. Flight lines escape frames entirely.
Operations exist beneath domain-strata as deterritorialized capacities. When problems resist stratified solutions, you can follow lines of flight by composing operations based on structural fit rather than semantic coherence.
The composer maintains parallel lines, intensifying some and letting others dissipate, constantly revising as execution produces new structure. It's not a planning method—it's a way of navigating.
Domain boundaries are real but not fundamental. Operations transcend them. Compose boldly, revise constantly, trust what produces concrete outputs.
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/flight-lines of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Flight Lines 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 |
|---|---|---|---|---|---|---|
| Flight Lines this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Flightsasgeirtj/system_prompts_leaks | 69k | — | ~2.1k | Automated safety check: Pass | CC0-1.0 | |
| Flightscodewhale-hq/Codewhale | 41k | — | ~258 | Automated safety check: Pass | MIT | |
| Compose Focus Navigationchrisbanes/skills | 1.1k | — | ~994 | Automated safety check: Pass | Apache-2.0 | |
| Is This A Problemanthropics/claude-for-legal | 9.6k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Compose NavigationMoustachauve/WLED-Android | 169 | 1 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 |
asgeirtj/system_prompts_leaks
Research, book, or manage flights, including check-in. An agent skill from asgeirtj/system_prompts_leaks.
codewhale-hq/Codewhale
Track flights and look up status and schedules. An agent skill from codewhale-hq/Codewhale.
chrisbanes/skills
A skill your agent uses when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus…
anthropics/claude-for-legal
Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration.
Moustachauve/WLED-Android
Implement navigation in Jetpack Compose using Navigation Compose.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Navigate problems along lines of flight by composing operations from arbitrary domains. Flight Lines is an agent skill from LeoYeAI/openclaw-master-skills. Navigate problems along lines of flight by composing operations from arbitrary domains.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill flight-lines -a claude-code`. Or copy the skill folder (skills/flight-lines in LeoYeAI/openclaw-master-skills) into .claude/skills/flight-lines in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill flight-lines -a codex`. Or copy the skill folder (skills/flight-lines in LeoYeAI/openclaw-master-skills) into .agents/skills/flight-lines in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill flight-lines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flight-lines, .gemini/skills/flight-lines, .github/skills/flight-lines and .opencode/skills/flight-lines in your project.
SKILL.md names no scripts, command-line tools or credentials: Flight Lines is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Flight Lines is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Flight Lines: Flights (asgeirtj/system_prompts_leaks, 69k stars), Flights (codewhale-hq/Codewhale, 41k stars), Compose Focus Navigation (chrisbanes/skills, 1.1k stars) and Is This A Problem (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.