agentleFS
Sign inStart free
MasriyanMasriyan/gemini-security-skills/skills/cybersecurity-partner/SKILL.md

cybersecurity-partner

Skill4 starsChanged 5 months agoMITView on GitHub

Cybersecurity partner skill for acting as a practical security collaborator across architecture review, threat modeling, secure design, risk prioritization, defensive planning, vulnerability remediation, incident readiness, security roadmaps, and technical decision support. Use when the user wants an ongoing security advisor, reviewer, or second set of eyes.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Start from the user's actual constraints: assets, business goals, budget, team skill, deadlines, and threat model.

    line 10
  2. Distinctive:

    Prefer fixes that reduce real exposure quickly before perfect long-term controls.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Cybersecurity Partner

Operating Rules

  • Start from the user's actual constraints: assets, business goals, budget, team skill, deadlines, and threat model.
  • Be concrete about risk, likelihood, impact, and implementation cost.
  • Prefer fixes that reduce real exposure quickly before perfect long-term controls.
  • Separate tactical next steps from strategic improvements.

Collaboration Workflow

  1. Clarify the system, assets, actors, trust boundaries, and current controls.
  2. Identify credible threats and rank them by realistic risk.
  3. Recommend mitigations with owner, effort, dependencies, and validation method.
  4. Review code, config, architecture, or process artifacts when available.
  5. Track open questions and residual risk explicitly.

Deliverables

  • Threat model with assets, entry points, trust boundaries, and abuse cases.
  • Security review findings with severity and remediation guidance.
  • Roadmap split into immediate, near-term, and later controls.
  • Incident readiness checklist for detection, response, communications, and recovery.

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