intro
Skill6 starsChanged 2 months agoMITView on GitHub
Introduce two or more people from the owner's network: resolve and confirm both identities, DM each side for consent before any group exists, then create the group and introduce both sides inside it. Requires the owner's approval first. Triggers: "/intro", "introduce X and Y", "connect X with Y".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- manor-os/manor-aitheir own version, first seen Oct 31, 2026
- jorekai/skillstheir own version, first seen Sep 7, 2026
- noticedso/skillstheir own version, first seen Aug 24, 2026
- ttalkkaklab/social-flowtheir own version, first seen Aug 18, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- manor-os/manor-ai★ 158same name
- noticedso/skills★ 2same name
- ttalkkaklab/social-flow★ 1same name
- jorekai/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository100 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 03Skill
- 1Skill
- agendaSkill
- alfa-search-recall-deepresearchSkill
- alpha-judgeSkill
- alpha-reviewSkill
- archSkill
- askSkill
- bibleSkill
- brainSkill
- busSkill
- canon-revisionSkill
- ccSkill
- chatgpt-syncSkill
- chat-searchSkill
- chatSkill
- claudeai-syncSkill
- coachSkill
- codex-mirrorSkill
- codex-reviewSkill
- cofounderSkill
- cofounder-watchSkill
- commentsSkill
- community-alphaSkill
- content-mineSkill
- crm-syncSkill
- declinedSkill
- dedupSkill
- defuddleSkill
- dr-fanoutSkill
- episodeSkill
- faaa-syncSkill
- faSkill
- fb-postSkill
- fb-replySkill
- fb-watchSkill
- findSkill
- fireflies-syncSkill
- five-hardSkill
- fleetSkill
- follower-onboardSkill
- geminiSkill
- gitbook-importSkill
- gmailSkill
- granola-syncSkill
- handoffSkill
- health-syncSkill
- inboxSkill
- intakeSkill
- intentionSkill
- issue-matchSkill
- journeySkill
- last30daysSkill
- local-chatgpt-token-healSkill
- mcpSkill
- migrateSkill
- mine-channelSkill
- n8nSkill
- notebooklmSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Wait for their "+". Do NOT create anything before that.
- Distinctive: line 42
No long dashes anywhere (use a colon, comma, or parentheses).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/intro: warm-introduction automation
The operator's matchmaking is a conveyor: a warm intro is the product they trade. This skill turns "introduce X to Y" into one repeatable operation, run from their Telegram account.
Proven live 2026-06-19 (test pair Rita @teammate_r + Nataly @teammate_n). Standing rules live in memory [[intro-automation]] and [[no-long-dashes]].
Flow
1. RESOLVE both people
For each name, identify the real person before doing anything:
/findornamesearchover names.db, the Platinum CRMleads/contacts, and Telegramresolve_username/search_contacts.- Disambiguate name collisions (the operator has many same-name contacts: 8 Denises, several Karim) using
get_common_chats, company, recent calls. - Capture for each: real name, @handle, tg_id, company, and the Latin first name for the title.
2. CONFIRM (DEFAULT: ON, approval required)
Show the operator a compact BEFORE→AFTER block:
- who each person resolved to (name, @handle, company),
- the exact group title that will be created,
- which account will send. Wait for their "+". Do NOT create anything before that. Skip this gate ONLY if the operator explicitly says "no approval needed" in the request.
3. CREATE the group
create_groupfrom the chosen account, title =LatinName1 <> LatinName2 <> Palo Alto Research Lab.- The
<>sign goes between ALL elements. Names are LATIN only, taken from the lead's own name. Pass the title with plain<>AT creation. Never HTML-escape it. Never rely on renaming afterward (see gotchas). - Account label "default" = @work_acct_a (id 226258979); "corp_acct" is the company voice. Pick the account with the warmest existing thread to each lead.
4. INTRO blurb in the group
- Right after creating the group, get its invite link via
export_chat_invite. - Short, warm, in the operator's voice. State who each person is and why they are a fit, INCLUDE the group link ("Group:
<link>"), close with "over to you two". - LANGUAGE: write to each lead in THEIR language. A Russian-speaking lead gets Russian, an English-speaking lead gets English. Detect language from the CRM card (country / language field), the vault person note, or the prior DM-thread language. If the two leads share no common language, write the group blurb bilingually (RU plus EN).
- No long dashes anywhere (use a colon, comma, or parentheses). See [[no-long-dashes]].
5. DM each side
- A one-line personal heads-up to each participant, written IN THAT PERSON'S language, including the group invite link so they can jump straight in.
6. LOG and close the loop
- Mark both in the Platinum CRM at the INTRO stage.
- Set a watcher to close the loop later ("how did the conversation go?", the operator's double-intro rule).
Telegram-MCP connector gotchas
edit_chat_titleFAILS on basic groups (CHAT-ERR-838): you cannot rename after creation, so always create with the final correct title in one shot.- There is no delete for Telegram basic groups, only
leave_chat(which leaves a ghost group for the others). Get the title right the first time. - Adding mutual contacts works. If a non-contact's privacy blocks adding, fall back to
export_chat_inviteand send the link. - Pace intros one at a time with gaps (anti-ban). Never mass-create.
Hard stops (defer to operating-agreement + bible)
Pause and ask the operator when an intro carries money, a commitment, secrets, or would be a mass blast. A plain social intro with no such payload is fine to run after their approval.
Report to the operator
Short summary of what was created plus the group title and who is in it, then a 🧒 In plain words recap. No long dashes.
<!--kit-footer-->Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

