Skip to content
TrustedSkillsbeta
Back to all skills

Dependency Analyzer

Checked
lis186·vlatest·backend·MIT

This tool analyzes text to identify grammatical dependencies between words, aiding in understanding sentence structure and improving writing clarity.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add lis186/sourceatlas --skill dependency-analyzer -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

lis186

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned lis186/sourceatlas at b176ae0f1c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 47 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The lis186-dependency-analyzer skill helps analyze dependencies within a project. It identifies and lists external libraries or packages that a codebase relies on, providing insights into potential conflicts or vulnerabilities. This tool is particularly useful for understanding the structure of unfamiliar projects or preparing for upgrades.

When to use it

  • Project onboarding: Quickly understand the external dependencies used in a new project you're joining.
  • Security audits: Identify potentially vulnerable libraries that need updating.
  • Dependency management: Generate lists of dependencies for documentation or package management tools.
  • Code refactoring: Analyze existing dependencies before making significant changes to a codebase.

Key capabilities

  • Dependency listing
  • Project analysis
  • External library identification

Example prompts

  • "List the dependencies in this Python project."
  • "What external libraries does this Node.js application use?"
  • "Analyze the dependencies of this Java project and report any potential vulnerabilities."

Tips & gotchas

The skill requires access to the codebase being analyzed. Ensure the AI agent has appropriate permissions or file access for accurate results.