Skip to content
TrustedSkillsbeta
Back to all skills

Cybersecurity Analyst

Checked
rysweet·vlatest·security

This Cybersecurity Analyst skill simulates a security expert, identifying potential threats and vulnerabilities to proactively protect your systems.

Repository

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 rysweet/amplihack --skill cybersecurity-analyst -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

rysweet

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 rysweet/amplihack at 84424457d5.

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

Commit
84424457d5
Manifest
.claude/skills/cybersecurity-analyst/SKILL.md
Scanned
8 files, 5,374 lines
Copies in repo
2 — all of them scanned
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 cybersecurity-analyst skill equips AI agents with the ability to analyze potential security threats, detect anomalies in network traffic, and provide insights into vulnerabilities. It can interpret logs, identify suspicious activity, and suggest mitigation strategies based on known attack patterns.

When to use it

  • To investigate unusual login attempts or access patterns in a company's internal systems.
  • When analyzing firewall or intrusion detection system (IDS) logs for signs of malicious behavior.
  • During incident response efforts to determine the scope and impact of a security breach.

Key capabilities

  • Analyzes network traffic and log files for suspicious activity
  • Identifies potential threats based on known attack signatures
  • Provides recommendations for mitigating identified risks

Example prompts

  • "Analyze this firewall log for signs of unauthorized access."
  • "What could be the cause of these repeated failed login attempts?"
  • "Review the system logs and identify any unusual behavior over the past 24 hours."

Tips & gotchas

  • Ensure that the AI agent has access to relevant security databases or threat intelligence feeds for accurate analysis.
  • Be cautious when interpreting results—always validate findings with additional tools or expert review.