agentleFS
SrejonKhanSrejonKhan/agent-skills/skills/repo_infographic/SKILL.md

repo_infographic

Skill3 starsChanged 2 months agoMITView on GitHub

Generates a crisp, clear full infographic of the repository with a unique theme based on the repo's content. Saves the infographic to the assets folder and links it in the README.md file.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to create a comprehensive infographic of the current repository.

    line 8
  2. Very specific:

    Use the generate_image tool to create a visual infographic.

    line 17
  3. Very specific:

    Ensure the generated image is saved, downloaded, or moved to this assets directory.

    line 23
  4. Distinctive:

    When generating the prompt for the infographic, consider:

    line 31
  5. Distinctive:

    Visual Hierarchy: Use size, color, and contrast to denote importance (e.g., the core processing engine should be larger and more central …

    line 34
  6. Very specific:

    Brand Alignment: If a DESIGN_PHILOSOPHY.md exists, ensure the infographic adopts the brand's aesthetic (e.g., "Cyberpunk", "Minimalist …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Repo Infographic

Use this skill to create a comprehensive infographic of the current repository.

Workflow

  1. Analyze Repository:
    • Understand the current repository structure, purpose, and key components using directory listings and file analysis.
    • Determine a unique and appropriate visual theme for the infographic based on the repository's main focus.
  2. Generate Infographic:
    • Use the generate_image tool to create a visual infographic.
    • The prompt should request a crisp, clear infographic that visualizes the repository's modules, features, or architecture, heavily leaning into the determined theme.
    • Provide the ImageName as repo_infographic.
  3. Save Asset:
    • Locate the assets folder in the repository root (create it if it doesn't exist).
    • Ensure the generated image is saved, downloaded, or moved to this assets directory.
  4. Update README.md:
    • Identify the main README.md file of the repository.
    • Append or insert an embedded image link to the generated infographic pointing to the correct relative path in the assets folder.

Advanced Infographic Patterns

When generating the prompt for the infographic, consider:

  • Thematic Storytelling: The image should tell a story (e.g., "Data Flow", "Component Architecture") rather than just being a random collection of boxes.
  • Visual Hierarchy: Use size, color, and contrast to denote importance (e.g., the core processing engine should be larger and more central than utility scripts).
  • Brand Alignment: If a DESIGN_PHILOSOPHY.md exists, ensure the infographic adopts the brand's aesthetic (e.g., "Cyberpunk", "Minimalist Corporate").

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.