Manage Settings
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
Setting up a hyperlocal mutual aid network with neighbors. An agent skill from LeoYeAI/openclaw-master-skills.
$ npx skills add LeoYeAI/openclaw-master-skills --skill neighbor-mutual-aid -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills neighbor-mutual-aid --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/neighbor-mutual-aid .claude/skills/neighbor-mutual-aid && 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 "neighbor-mutual-aid" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/neighbor-mutual-aid into .claude/skills/neighbor-mutual-aid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neighbor-mutual-aid", 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/neighbor-mutual-aidType 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 neighbor-mutual-aid -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills neighbor-mutual-aid --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/neighbor-mutual-aid .agents/skills/neighbor-mutual-aid && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "neighbor-mutual-aid" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/neighbor-mutual-aid into .agents/skills/neighbor-mutual-aid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neighbor-mutual-aid", 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 neighbor-mutual-aid -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills neighbor-mutual-aid --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/neighbor-mutual-aid .cursor/skills/neighbor-mutual-aid && 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 "neighbor-mutual-aid" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/neighbor-mutual-aid into .cursor/skills/neighbor-mutual-aid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neighbor-mutual-aid", 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/neighbor-mutual-aid--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 neighbor-mutual-aid -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills neighbor-mutual-aid --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/neighbor-mutual-aid .gemini/skills/neighbor-mutual-aid && 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 "neighbor-mutual-aid" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/neighbor-mutual-aid into .gemini/skills/neighbor-mutual-aid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neighbor-mutual-aid", 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 neighbor-mutual-aidInstalls 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 neighbor-mutual-aid -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/neighbor-mutual-aid .github/skills/neighbor-mutual-aid && 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 "neighbor-mutual-aid" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/neighbor-mutual-aid into .github/skills/neighbor-mutual-aid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neighbor-mutual-aid", 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 neighbor-mutual-aid -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 neighbor-mutual-aid --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/neighbor-mutual-aid .opencode/skills/neighbor-mutual-aid && 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 "neighbor-mutual-aid" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/neighbor-mutual-aid into .opencode/skills/neighbor-mutual-aid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neighbor-mutual-aid", 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.
neighbor-mutual-aidSetting up a hyperlocal mutual aid network with neighbors. An agent skill from LeoYeAI/openclaw-master-skills.
Neighbor Mutual Aid is an agent skill from LeoYeAI/openclaw-master-skills. Setting up a hyperlocal mutual aid network with neighbors. Use when someone wants to build community resilience, organize neighbors for mutual support, share resources, or create emergency preparedness networks on their block or in their building.
Its SKILL.md is about 4.1k 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.
7 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 (its code samples are yaml and agent-adaptation).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
mutualaidhub.orgready.govbigdoorbrigade.comanthropic.comFrom 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.
Neighbor Mutual Aid loads about 4.1k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 740 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). 740 words, ~4,101 tokens.
.claude/skills/neighbor-mutual-aid/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Most people live within 50 feet of others and know almost none of them. A mutual aid network is not a political project or a commune -- it's a practical arrangement where nearby humans agree to share resources, watch out for each other, and coordinate during emergencies. The setup takes one afternoon of door-knocking and one sheet of paper. The payoff is knowing who has a truck when you need to move something, who's a nurse when someone falls, and who can grab your kid from school if you're stuck at work.
# Localization note
- Community structures, housing types, and cultural norms around neighbor contact vary hugely
- Apartment building (buzz intercom, leave flyer under doors, talk to building manager first)
vs. suburban block (walk up to front doors) vs. rural (longer distances, fewer neighbors, more self-reliance)
- Cultural directness norms differ: in some cultures, knocking unannounced is normal;
in others, a written note first is more appropriate
- Adjust for local emergency numbers (911 in US, 999 in UK, 112 in EU, 000 in Australia)
- Swap local disaster types (earthquake, hurricane, tornado, bushfire, flooding)
- Group purchasing sources and co-op structures vary by countryAgent action: Help the user create a simple map of their immediate neighborhood -- who lives where and what they already know about them.
BLOCK MAPPING EXERCISE (15 minutes)
Draw a rough sketch of your block or building floor. For each unit/house:
1. Write the address or unit number
2. Write names if you know them (first name is fine)
3. Note anything you already know:
- Approximate age range (young family, retired, etc.)
- Pets (you'll see them outside)
- Vehicles (truck owners are gold for mutual aid)
- Visible skills (someone always doing yard work = gardening knowledge)
DON'T OVERTHINK THIS. You're not surveilling anyone.
You're just writing down what you already passively know.
Target: 8-15 households for a suburban block, 6-10 for an apartment floorAgent action: Provide the user with a tested door-knocking script and coach them on the approach. This is the hardest part -- most people are nervous about it. Normalize that.
DOOR-KNOCK PROTOCOL
When to go: Saturday or Sunday, 10am-12pm or 4-6pm
What to bring: A one-page flyer (template below) and a pen
What to wear: Normal clothes. Not a clipboard-and-lanyard vibe.
OPENING SCRIPT (adjust to your personality):
"Hi, I'm [name], I live at [address/unit]. I'm putting together a
neighborhood contact list -- just so we know each other and can help
out in emergencies or share resources. Takes about 2 minutes. Would
you be interested?"
IF THEY SAY YES:
Walk through the 5-question survey (Step 3).
Leave them the flyer. Ask for their preferred contact method.
IF THEY SAY NO OR SEEM UNCOMFORTABLE:
"No problem at all. Here's my number if you ever need anything."
Hand them the flyer and move on. No pressure. Ever.
IF NOBODY'S HOME:
Leave the flyer with a handwritten note:
"Hi neighbor -- I'm [name] at [address]. Putting together a block
contact list for emergencies and resource sharing. Text me if
you're interested: [phone number]"
EXPECT: About 60-70% positive response rate. Some people will be
thrilled someone finally did this. Some won't be interested. Both
are fine.Agent action: Generate a simple survey the user can fill out during each conversation. This is the core data-gathering step.
NEIGHBOR RESOURCE SURVEY
(Fill out during the door-knock conversation. Keep it casual.)
Name: _______________ Address/Unit: _______________
Phone: _______________ Email (optional): _______________
Preferred contact method: Text / Call / Email / Signal / WhatsApp
1. SKILLS: Do you have any medical training, mechanical skills,
trade skills, or other expertise? (nurse, electrician, plumber,
EMT, teacher, IT, etc.)
_______________________________________________
2. EQUIPMENT: Do you have any of these you'd be willing to lend
occasionally? (Check all that apply)
[ ] Truck/van/trailer [ ] Ladder (what height? ___)
[ ] Power tools [ ] Generator
[ ] Chainsaw [ ] First aid kit
[ ] Jumper cables [ ] Snow blower
[ ] Lawn mower [ ] Other: _______________
3. EMERGENCY: Is there anyone in your household who might need
extra help in an emergency? (Elderly person, infant, someone
with mobility issues, medication-dependent, etc.)
_______________________________________________
4. AVAILABILITY: Would you be open to any of these?
[ ] Emergency contact exchange (call me if something's wrong)
[ ] Key exchange (I can check on your place when you travel)
[ ] Tool/equipment lending
[ ] Group purchasing (bulk food, supplies)
[ ] Babysitting/childcare swap
[ ] Pet care coverage (feed cat, walk dog when you're away)
[ ] Seasonal help (snow removal, storm prep, yard work)
5. OTHER: Anything else you'd want from a neighborhood network?
_______________________________________________Agent action: Compile survey results into a one-page resource sheet. Generate it as a formatted document the user can print and distribute.
NEIGHBORHOOD RESOURCE SHEET (template)
[YOUR BLOCK/BUILDING NAME] -- Emergency & Resource Contacts
Last updated: [DATE]
EMERGENCY CONTACTS:
- Fire/Police/Ambulance: 911
- Poison Control: 1-800-222-1222
- Non-emergency police: [local number]
NEIGHBOR CONTACT LIST:
Name | Address | Phone | Key Skills/Resources
______________|_________|______________|____________________
| | |
| | |
| | |
(continue for all participating neighbors)
SHARED RESOURCES AVAILABLE:
- Truck/trailer: [Name, phone]
- Generator: [Name, phone]
- Ladder (extension): [Name, phone]
- Medical training: [Name, phone]
- Mechanical/trade skills: [Name, phone]
SEASONAL COORDINATION:
- Snow removal rotation: [names]
- Storm prep lead: [name]
- Yard waste coordination: [name]
EMERGENCY PLAN:
- Meeting point (if evacuation needed): [location]
- Who checks on who:
[Name] checks on [Name] (elderly/needs assistance)
[Name] checks on [Name]
PRINT THIS. Put it on your fridge. Give a copy to every
participating household.Agent action: Based on survey responses, help the user set up whichever exchange systems neighbors expressed interest in.
TOOL/EQUIPMENT LENDING LIBRARY
Simple system -- no apps needed:
1. Create a shared note (Google Doc, group text, or physical binder)
2. List every item available for lending and who owns it
3. Rules:
- Text the owner to borrow, return within 48 hours
- Return clean and in working order
- If you break it, you replace it or pay for repair
- No lending to non-network people without owner's OK
GROUP PURCHASING
Best items for bulk buying:
- Paper products (toilet paper, paper towels) -- 30-40% savings
- Cleaning supplies -- 25-35% savings
- Non-perishable food (rice, beans, canned goods) -- 20-30% savings
- Seasonal supplies (salt, firewood, garden soil) -- 20-40% savings
How to run it:
1. One person places the Costco/warehouse order
2. Split cost proportionally
3. Distribute from one location (garage, lobby)
4. Rotate who places the order each month
5. Use Splitwise or Venmo to settle up
BABYSITTING/CHILDCARE EXCHANGE
Credit system works best:
1. Track hours with a shared spreadsheet
2. 1 hour of watching = 1 credit
3. Use credits to get coverage from another parent
4. Maximum "debt" of 5 hours before you need to give back
5. Emergency coverage (sick kid, stuck at work) doesn't cost credits
6. All participating parents meet first so kids know every adult
PET CARE COVERAGE
1. Exchange house keys or provide lockbox codes
2. Each pet owner writes a one-page care sheet:
- Feeding schedule, amounts, brand
- Medication if any
- Vet name and number
- Behavioral notes (leash reactive, hides under bed, etc.)
3. Do a practice run while you're home so the pet knows the neighborAgent action: If the user lives in an apartment building, adapt the approach for that context.
APARTMENT BUILDING ADAPTATION
Different challenges, same concept.
GETTING STARTED:
- Talk to building manager first. Some buildings have rules about
door-to-door contact. Get permission or at least a heads-up.
- Use the mailroom, lobby, or laundry room as your "town square"
- Post a flyer on the community board before knocking
- Start with your floor only, then expand
WHAT CHANGES:
- No tool lending library (storage is the issue -- keep it small)
- Package watching is the #1 easy win (accept packages for each other)
- Noise coordination matters (text before a party, agree on quiet hours)
- Emergency check-ins are more critical (people can be isolated for days
in apartments without anyone noticing)
- Shared laundry scheduling can reduce conflict
- Group purchasing works great (one delivery split across units)
WHAT STAYS THE SAME:
- Emergency contact exchange
- Skills inventory
- Key exchange for emergencies
- Pet care and childcare swaps
- The fundamental pitch: "We live 10 feet apart. We should at least
know each other's names."Agent action: Help the user set up lightweight maintenance so the network doesn't die after the first month.
KEEPING IT ALIVE (minimal effort version)
QUARTERLY:
- Update the contact sheet (new neighbors, moves, changed numbers)
- One casual gathering per season (doesn't have to be fancy --
front yard hangout, building lobby coffee, block party)
ANNUALLY:
- Refresh the resource survey (people get new tools, learn new skills)
- Review and update emergency plans
- Restock shared emergency supplies if applicable
ONGOING:
- Group text/chat for time-sensitive things (storm warning, suspicious
activity, lost pet, "does anyone have a Phillips head screwdriver")
- Use the network. Borrow the ladder. Ask for help moving the couch.
The more people use it, the stronger it gets.
- Welcome new neighbors. Knock on their door within the first month.
Give them the resource sheet. This is how the network grows.
WHO COORDINATES:
- You started it, so you're the coordinator for now
- After 6 months, ask if someone else wants to share or take over
- It doesn't need a leader. It needs someone willing to send
the occasional group text.mutual_aid:
network_status: null
block_mapped: false
households_contacted: 0
households_participating: 0
contact_sheet_created: false
exchanges_active:
tool_lending: false
group_purchasing: false
childcare_swap: false
pet_care: false
emergency_contacts: false
key_exchange: false
housing_type: null
last_updated: null
next_gathering: null
coordinator: nulltriggers:
- name: seasonal_coordination
condition: "network_status IS 'active'"
schedule: "quarterly"
action: "Time for a seasonal check-in with your neighborhood network. Update the contact sheet, plan a casual gathering, and coordinate any seasonal needs (storm prep, snow removal rotation, yard waste, etc.)."
- name: new_neighbor_welcome
condition: "network_status IS 'active' AND user_reports_new_neighbor"
action: "A new neighbor moved in. Within the first two weeks, knock on their door with the resource sheet and introduce the network. First impressions set the tone -- keep it casual and low-pressure."
- name: network_revival
condition: "network_status IS 'active' AND last_updated > 90 days"
action: "Your neighborhood network hasn't had any activity in 3 months. Send a group text with something simple -- a weather warning, a question, or an invite to a front-yard hangout. Networks stay alive through use."
- name: emergency_prep_check
condition: "network_status IS 'active'"
schedule: "annually"
action: "Annual emergency preparedness review for your neighborhood network. Refresh the resource survey, update emergency contacts, review who checks on who during emergencies, and verify everyone still has the current contact sheet."© 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/neighbor-mutual-aid of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Neighbor Mutual Aid 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 |
|---|---|---|---|---|---|---|
| Neighbor Mutual Aid this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Manage Settingsasgeirtj/system_prompts_leaks | 69k | — | ~3.1k | Automated safety check: Pass | CC0-1.0 | |
| Warp Settings Editorwarpdotdev/warp | 65k | 1 repos | ~675 | Automated safety check: Pass | AGPL-3.0 | |
| Warp Settings Page Builderwarpdotdev/warp | 65k | 1 repos | ~4.5k | Automated safety check: Pass | AGPL-3.0 | |
| Add Server Env Var for User Settinglobehub/lobehub | 83k | — | ~644 | Automated safety check: Pass | Custom licence | |
| Add Settings Pagesimstudioai/sim | 30k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
warpdotdev/warp
Finds and changes Warp application settings by searching a bundled JSON schema and editing the matching TOML settings file at the right nesting depth.
warpdotdev/warp
How to build a settings page in the Warp desktop client so widgets, page titles and settings search behave correctly, and which common mistakes to avoid.
lobehub/lobehub
Adds a server-side environment variable that sets the default for a user setting in LobeHub, wired from the env schema through server config to the user store and docs.
simstudioai/sim
Add a new Sim settings page, or audit existing settings pages for design-system compliance with the shared SettingsPanel layout.
anthropics/claude-plugins-official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
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.
Setting up a hyperlocal mutual aid network with neighbors. An agent skill from LeoYeAI/openclaw-master-skills. Neighbor Mutual Aid is an agent skill from LeoYeAI/openclaw-master-skills. Setting up a hyperlocal mutual aid network with neighbors.
Neighbor Mutual Aid fits situations like: someone wants to build community resilience; organize neighbors for mutual support; share resources; create emergency preparedness networks on their block.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill neighbor-mutual-aid -a claude-code`. Or copy the skill folder (skills/neighbor-mutual-aid in LeoYeAI/openclaw-master-skills) into .claude/skills/neighbor-mutual-aid in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill neighbor-mutual-aid -a codex`. Or copy the skill folder (skills/neighbor-mutual-aid in LeoYeAI/openclaw-master-skills) into .agents/skills/neighbor-mutual-aid 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 neighbor-mutual-aid -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/neighbor-mutual-aid, .gemini/skills/neighbor-mutual-aid, .github/skills/neighbor-mutual-aid and .opencode/skills/neighbor-mutual-aid in your project.
SKILL.md names no scripts, command-line tools or credentials: Neighbor Mutual Aid is instructions for the agent only. Our summary lists: Node.js.
SKILL.md names 4 domains. As links in the text: mutualaidhub.org, ready.gov, bigdoorbrigade.com and anthropic.com. 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.
Neighbor Mutual Aid 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.1k tokens (SKILL.md is roughly 16k 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 Neighbor Mutual Aid: Manage Settings (asgeirtj/system_prompts_leaks, 69k stars), Warp Settings Editor (warpdotdev/warp, 65k stars), Warp Settings Page Builder (warpdotdev/warp, 65k stars) and Add Server Env Var for User Setting (lobehub/lobehub, 83k 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,161 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.