agentleFS
Sign inStart free
TimCodes04TimCodes04/second-brain/.claude/skills/connect/SKILL.md

connect

Skill1 starsChanged 51 days agoMITView on GitHub

Discover non-obvious, cross-domain connections between vault notes and write them as real wikilinks into both notes' Related sections — making hidden structure visible in the graph.

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use connect-apps, skill-share and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    connect-apps

    Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.

    Also in 19 projects that use this

  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 17 projects that use this

  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • trendinuxSkill

    twitter-algorithm-optimizer

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

    Also in 12 projects that use this

  • LangChainSkill

    langsmith-fetch

    Fetches LangSmith traces for debugging agent behavior. Use when troubleshooting agent issues, reviewing conversation history, or investigating tool calls.

    Also in 18 projects that use this

  • +1 more from ComposioHQ
  • +5 more from ArogyaReddy

The file

Create a free account to mount
Files
SKILL.md

/connect [--course <slug> | --all]

Cross-domain link discovery. Read docs/vault-schema.md first. Vault: <vault>.

  1. Harvest the corpus (cheap, no embeddings): for every content note in scope (--course limits to that course's notes + all concepts/; default --all = every course/concept/MOC/reference/project note; skip templates/, card and problem files, and the system notes Home.md, Inbox.md, log/inbox-archive.md, palace/_Palace Guide.md), collect one line: title | type | domains | summary from frontmatter. Include Profile.md — connections to the user's current work are the most valuable kind. Also grep each note's existing wikilinks so already-linked pairs are excluded.
  2. Propose: from the corpus, generate candidate pairs that are non-obvious and cross-domain — same mathematical structure, transferable technique, same phenomenon in different clothes (e.g. damped oscillator ↔ RLC circuit ↔ posterior width in inference). Each candidate: the pair + a one-sentence mechanism. Obvious within-topic pairs (already same course/section) don't count. Aim for quality: 3–10 candidates, ranked.
  3. Confirm in the terminal: present the ranked list; the user picks (numbers, "all", or "none").
  4. Write: for each accepted pair, append to BOTH notes' ## Related sections: - [[Other Note]] — <one-line mechanism> (create the section if missing; no duplicates; bump updated:). These are real wikilinks → real edges in graph view.
  5. Optional bridge cards: for striking connections, offer a card ("What do X and Y have in common structurally?") into concepts/Inbox Cards.md per the /card procedure.
  6. Report: links written, and any cluster observations worth a future MOC section.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free