Find Leads
eracle/OpenOutreach
Find qualified B2B leads with OpenOutreach — run openoutreach find N [emails], read the CSV it prints on stdout, and hand the rows to whatever sends.
Plan and promote an open house that draws buyers and generates leads.
$ npx skills add mohitagw15856/pm-claude-skills --skill open-house-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills open-house-plan --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/open-house-plan .claude/skills/open-house-plan && 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 "open-house-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-plan into .claude/skills/open-house-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-house-plan", 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/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-planType 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 mohitagw15856/pm-claude-skills --skill open-house-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills open-house-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/open-house-plan .agents/skills/open-house-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "open-house-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-plan into .agents/skills/open-house-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-house-plan", 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 mohitagw15856/pm-claude-skills --skill open-house-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills open-house-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/open-house-plan .cursor/skills/open-house-plan && 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 "open-house-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-plan into .cursor/skills/open-house-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-house-plan", 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/mohitagw15856/pm-claude-skills.git --path skills/open-house-plan--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 mohitagw15856/pm-claude-skills --skill open-house-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills open-house-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/open-house-plan .gemini/skills/open-house-plan && 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 "open-house-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-plan into .gemini/skills/open-house-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-house-plan", 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 mohitagw15856/pm-claude-skills open-house-planInstalls 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 mohitagw15856/pm-claude-skills --skill open-house-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/open-house-plan .github/skills/open-house-plan && 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 "open-house-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-plan into .github/skills/open-house-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-house-plan", 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 mohitagw15856/pm-claude-skills --skill open-house-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills open-house-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/open-house-plan .opencode/skills/open-house-plan && 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 "open-house-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/open-house-plan into .opencode/skills/open-house-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-house-plan", 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.
open-house-planPlan and promote an open house that draws buyers and generates leads.
Open House Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan and promote an open house that draws buyers and generates leads. Use when asked to plan an open house, market an open house, or create an open-house checklist. Produces a plan — timing and promotion across channels, prep and staging checklist, a day-of run sheet, lead capture, and follow-up — so the event drives real interest and the agent leaves with leads, not just foot traffic.
Its SKILL.md is about 990 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 Marketing & SEO, covering Lead generation. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
Read from SKILL.md and the folder at commit 1cbf1f0. 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.
Open House Plan loads about 988 tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 488 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 488 words, ~988 tokens.
.claude/skills/open-house-plan/SKILL.md (or your agent's skills folder).A good open house is a marketing event, not an unlocked door: promoted to the right buyers, staged to show well, and run to capture leads you follow up. This skill plans the whole thing — before, during, and after — so the agent maximises qualified traffic and walks away with a pipeline, not just a sign-in sheet.
Not quite this? Use
the-open-housewhen you are the buyer and want to rehearse an open house from the other side.
Given "plan an open house for my listing this Saturday", produce the full plan anyway — infer sensible timing, channels, and prep for the property type, marking specifics (insert) (address, date/time, price). Never invent property facts. Always include lead capture and follow-up — that's the point.
Ask for these only if they aren't already provided (else infer and label):
1. Timing — the recommended day/time (and why), plus any broker/neighbour preview.
2. Promotion plan — a channel-by-channel checklist with timing and the message:
| Channel | When | Action |
|---|---|---|
| MLS / portals | as listed | mark open house, strong photos |
| Social | 3–5 days before + day-of | post/story/boost to local audience |
| to buyer list/agents | invite | |
| Signage | day-of | directional signs, route from main road |
| Neighbours | days before | "tell a friend" invites |
3. Prep & staging checklist — clean, declutter, depersonalise, light, scent, fresh flowers, info sheets/flyers, secure valuables.
4. Day-of run sheet — arrival/setup time, greeting script, sign-in (lead capture), how to highlight features, handling questions, and safety.
5. Lead capture — how everyone signs in (digital form/QR), what to capture (name, contact, buying timeline, agent yes/no), and qualifying questions to ask.
6. Follow-up — a same-day/next-day plan: thank-you + feedback to every visitor, prioritise hot leads, and report to the seller (traffic, feedback, interest).
Real-estate marketing practice — multi-channel open-house promotion, staging, structured lead capture, and disciplined follow-up.
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/open-house-plan of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Open House Plan 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 |
|---|---|---|---|---|---|---|
| Open House Plan this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~988 | Automated safety check: Pass | MIT | |
| Find Leadseracle/OpenOutreach | 3.2k | — | ~4.6k | Automated safety check: Pass | GPL-3.0 | |
| 100m Leadsgetagentseal/founder-playbook | 729 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Business Contact and Social Links Finderbrowser-act/skills | 6.1k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| GitHub Lead GenDucksss/codex-profiles | 180 | — | ~1k | Automated safety check: Pass | MIT | |
| LinkedIn Ads Managementivangfalco/ads-skills | 279 | — | ~1.7k | Automated safety check: Pass | Custom licence |
eracle/OpenOutreach
Find qualified B2B leads with OpenOutreach — run openoutreach find N [emails], read the CSV it prints on stdout, and hand the rows to whatever sends.
getagentseal/founder-playbook
Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.
browser-act/skills
Finds a company's official website and social profiles from its name, or collects social links from a website URL, using BrowserAct templates run by a Python script.
Ducksss/codex-profiles
A skill your agent uses when running GitHub lead generation for codex-profiles.
ivangfalco/ads-skills
Routes LinkedIn Ads work for B2B SaaS to the right playbook: campaign planning, performance analysis, account audits, creative, scaling and account-based campaigns.
freekmurze/dotfiles
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness.
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Categories
Plan and promote an open house that draws buyers and generates leads. Open House Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan and promote an open house that draws buyers and generates leads.
Open House Plan fits situations like: asked to plan an open house; market an open house; create an open-house checklist.
Run `npx skills add mohitagw15856/pm-claude-skills --skill open-house-plan -a claude-code`. Or copy the skill folder (skills/open-house-plan in mohitagw15856/pm-claude-skills) into .claude/skills/open-house-plan in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mohitagw15856/pm-claude-skills --skill open-house-plan -a codex`. Or copy the skill folder (skills/open-house-plan in mohitagw15856/pm-claude-skills) into .agents/skills/open-house-plan 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 mohitagw15856/pm-claude-skills --skill open-house-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-house-plan, .gemini/skills/open-house-plan, .github/skills/open-house-plan and .opencode/skills/open-house-plan in your project.
SKILL.md names no scripts, command-line tools or credentials: Open House Plan 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.
Open House Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 988 tokens (SKILL.md is roughly 4k 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 Open House Plan: Find Leads (eracle/OpenOutreach, 3.2k stars), 100m Leads (getagentseal/founder-playbook, 729 stars), Business Contact and Social Links Finder (browser-act/skills, 6.1k stars) and GitHub Lead Gen (Ducksss/codex-profiles, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.