agentleFS
JunMA98JunMA98/Computer-science-claude-skills/skills/networkx/SKILL.md

networkx

Skill3 starsChanged 8 months agoMITView on GitHub

Build and analyze graphs in Python for CS research and engineering tasks. Use when working with citation graphs, dependency graphs, call graphs, knowledge graphs, agent tool graphs, communication networks, or any problem involving nodes, edges, graph algorithms, or network structure.

16 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 6

    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
  1. Distinctive:

    Use this skill for graph analysis that benefits from flexible Python-native data structures and readable algorithms.

    line 8
  2. Distinctive:

    Run the algorithms that answer the actual research question.

    line 24
  3. Distinctive:

    Read only what is needed:

    line 29
  4. Distinctive:

    Use NetworkX for clarity and experimentation, not maximum scale.

    line 38
  5. Distinctive:

    Do not assume a graph metric is meaningful unless it matches the graph semantics.

    line 41
  6. Distinctive:

    When the user asks for graph help without a fixed format, return:

    line 45

“Common” is measured: kept by at least 6 in 10 of the 16 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NetworkX

Use this skill for graph analysis that benefits from flexible Python-native data structures and readable algorithms.

Common CS Uses

  • citation or collaboration graph analysis
  • package dependency and call-graph analysis
  • knowledge graph or heterogeneous relation prototyping
  • graph features for downstream ML pipelines
  • path analysis in workflows, state machines, or tool graphs
  • synthetic graph generation for experiments or teaching

Workflow

  1. Define what nodes and edges represent.
  2. Attach attributes only when they affect the analysis.
  3. Choose the graph type: directed, undirected, multigraph, weighted, or heterogeneous approximation.
  4. Run the algorithms that answer the actual research question.
  5. Export or visualize only after the graph semantics are clear.

Local References

Read only what is needed:

  • references/graph-basics.md
  • references/algorithms.md
  • references/io.md
  • references/generators.md
  • references/visualization.md

Practical Guidance

  • Use NetworkX for clarity and experimentation, not maximum scale.
  • For very large graphs, use it for prototyping, sampling, or analysis on reduced representations.
  • Be explicit about directedness, edge weights, and disconnected components.
  • Do not assume a graph metric is meaningful unless it matches the graph semantics.

Default Output

When the user asks for graph help without a fixed format, return:

  1. the graph model being assumed
  2. the algorithms or metrics to compute
  3. interpretation notes and likely pitfalls

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.