Security

Security audits, vulnerabilities, compliance, auth, secrets, and safe automation

skills in category: 29,231
pages available: 1,218

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse security skills

Showing 3,025–3,048 of 29,231 skills

WelcomeADraft a first-contact orientation comment for a first-time contributor on a newly opened issue or PR on the configured `<upstream>` repo. Detects first-time authorship via the GitHub `author_association` field and drafts a welcome with contributing-guide link, community-norm pointers, and expected next steps. Waits for explicit maintainer confirmation before posting. Does not post for repeat contributors.securitypythongoVotes: 0GitHub stars: 108
Newcomer Issue ExplainerAGiven an open good-first-issue on the configured `<upstream>` repo, explain it in beginner terms and sketch a concrete approach: which files to read first, what "done" looks like, and where to ask follow-up questions — without writing any code or fix. First runs an issue assessment to confirm the issue is open, non-security, and scope-clear. Then drafts the explanation for maintainer review. Read-only; nothing is posted without explicit maintainer confirmation.securitypythonrustVotes: 0GitHub stars: 108
Good First Issue SweepASweep the open `<issue-tracker>` backlog for existing issues that could be labelled as good first issues. Classifies each candidate as READY (propose the GFI label), NEAR-MISS (surface edits to make it GFI-ready), or SKIP using the G1–G7 suitability rubric. Applies labels only after explicit maintainer confirmation; never edits issue bodies without the maintainer's direction.securitypythonrustVotes: 0GitHub stars: 108
Good First Issue AuthorADraft one net-new *good first issue* on the configured `<upstream>` repo from one supplied gap or small maintainer-named task. Run suitability and readiness checks before showing the draft. File via `gh` only after explicit maintainer confirmation. Never curate or relabel the existing backlog.securitypythonrustVotes: 0GitHub stars: 108
TriageAFor each open `<issue-tracker>` issue in the configured candidate pool, read the issue body and comments and classify the candidate disposition. On user confirmation, posts a triage-proposal comment that invites the project team to react. Read-only on tracker state — no workflow transitions, closures, or label changes. Six classes in the body.securitypythongoVotes: 0GitHub stars: 108
Stale SweepASweep open `<issue-tracker>` issues for inactivity past a configurable threshold and propose either a closure (when the issue has been unresponsive long enough to presume abandonment) or an update request (nudge the reporter to confirm the issue is still relevant). Waits for maintainer confirmation before posting any comment or closing anything.securitypythongoVotes: 0GitHub stars: 108
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
ReproducerAFor a single `<issue-tracker>` issue identifying a code-level bug, extract the reporter's example code from the issue body, adapt it to run on the current `<default-branch>`, execute via `<runtime>`, and compose a `verdict.json` describing the observed behaviour vs the expected failure. Read-only on the tracker — produces evidence, never posts. Invoked by `issue-triage` and `issue-reassess`; can also be run standalone.securitypythonrustVotes: 0GitHub stars: 108
ReassessASweep a configured pool of resolved or end-of-life `<issue-tracker>` issues and re-assess each against the current `<default-branch>`. Per-issue: invoke `issue-reproducer` to extract and run the reporter's code, classify the runtime outcome, attach a nature analysis, compose a `verdict.json`. Hand-back-on-completion contract: no comments posted, no transitions, no closures.securitypythongoVotes: 0GitHub stars: 108
Reassess StatsARead-only dashboard over a directory of `verdict.json` files produced by `issue-reassess` campaigns. Surfaces a health rating, classification distribution, partial-fix surfaces, oldest-unresolved buckets, and per-component breakdowns. Output is HTML by default; markdown fallback available. Read-only on tracker state; consumes campaign artefacts.securitypythongoVotes: 0GitHub stars: 108
Fix WorkflowAFor a single triaged `<issue-tracker>` issue confirmed as a bug or feature, draft a fix against `<upstream>` on `<default-branch>`. Produces the failing test, the smallest production change, the targeted+module test runs, and the commit. The PR is NOT opened on autopilot; the human committer reviews, signs, and pushes. Hand-back artefact summarises branch, commits, test results, and scope.securitypythongoVotes: 0GitHub stars: 108
DeduplicateAMerge two open `<issue-tracker>` issues that describe the same root cause, preserving both reporters' context. Proposes a closing comment on the duplicate and a cross-reference comment on the kept issue. Waits for maintainer confirmation before posting anything or closing anything.securitypythonrustVotes: 0GitHub stars: 108
Backlog StatsARead-only maintainer dashboard for the open general-issue backlog of <issue-tracker>. Surfaces a health rating, prioritised recommendations, age and staleness breakdowns, area pressure ranking, and a triage-funnel summary. Output is HTML by default; markdown fallback available.securitypythongoVotes: 0GitHub stars: 108
SentimentAMeasure contributor-sentiment signals on `<upstream>` over a window: thread tone, time-to-first-reply, first-PR retention, and reviewer load. Compares signals against baseline to generate a mode promotion gate report.securitypythonbashVotes: 0GitHub stars: 108
Onboarding ConciergeAAnswer newcomer contribution questions grounded in `CONTRIBUTING.md` and docs. Classifies questions into setup, workflow, first-issue, or maintainer hand-off. Drafts a concise response in the mentoring register. Read-only; never writes files or posts comments without maintainer confirmation.securitypythongoVotes: 0GitHub stars: 108
NominationARead-only nomination brief for a named contributor on <upstream>. Aggregates GitHub activity across contribution tracks, off-GitHub signal, and vendor-neutrality context for committer or PMC nomination threads. Surfaces information only: never rates the contributor or says whether they are ready.securitypythongoVotes: 0GitHub stars: 108
Contributor To CommitterARead-only brief showing a contributor's activity next to the project's committer or PMC reference levels, as plain numbers. Surfaces information only: no ranking, no status, no readiness verdict — the PMC decides.securitypythongoVotes: 0GitHub stars: 108
Committer OnboardingBPost-vote committer and PMC onboarding for Apache projects. Walks the nominator through every step from ICLA check to welcome announcement for both incubating podlings and graduated top-level projects, including mapping the new committer's GitHub handle to their Slack, Discord, and social-media identities for the nominator to confirm.securitypythonrustVotes: 0GitHub stars: 108
Activity SweepARead-only GitHub activity card for a named contributor on `<upstream>`. Summarizes PRs, reviews, issues, and comments over a configurable window. GitHub-visible activity only; use `contributor-nomination` for a full brief.securitypythonrustVotes: 0GitHub stars: 108
EducationAThis is a step-by-step guide to writing your first working skill in `<PROJECT>`. It takes you from "I have an idea" to "the pull request is merged". You do not need any earlier experience with the framework. This is not the full authoring reference. Once you know the shape of a skill, the [`write-skill`](../../skills/write-skill/SKILL.md) skill (you run it with `/magpie-utilities:write-skill`) takes you through every check, safety step, and packaging detail. Come back to it after your first s...securitypythongoVotes: 0GitHub stars: 108
TrainingA**Source page:** [Debugging a skill](../debugging-skills.md) **Estimated time:** 50 minutes (30 min reading + 20 min exercises and self-check) **Lesson in sequence:** 6 of 11 ---securitygodebuggingVotes: 0GitHub stars: 108
TrainingA**Source page:** [Your first skill](../your-first-skill.md) **Estimated time:** 60 minutes (40 min reading + 20 min exercises and self-check) **Lesson in sequence:** 4 of 11 ---securitygotestingVotes: 0GitHub stars: 108
Ai TutorsAPaste everything below the line into the system prompt field of any capable chat model (Claude, GPT, a local model, etc.). The learner then talks to it in the normal chat window. Nothing above the line is sent to the model. The prompt does two jobs. It runs the lesson as an interactive tutor, and it can regenerate or re-explain the lesson material on request. Both behaviours are defined below. The full source page (`docs/education/debugging-skills.md`, about 50 minutes: 30 reading, 20 exercis...securitygodebuggingVotes: 0GitHub stars: 108
Ai TutorsAPaste everything below the line into the system prompt field of any capable chat model (Claude, GPT, a local model, etc.). The learner then talks to it in the normal chat window. Nothing above the line is sent to the model. The prompt does two jobs. It runs the lesson as an interactive tutor, and it can regenerate or re-explain the lesson material on request. Both behaviours are defined below. This is a longer lesson than 1 to 3 (about 60 minutes: 40 reading, 20 exercises and self-check) and ...securitypythongoVotes: 0GitHub stars: 108
Vulnerability ResearchAACTIVATE when the user asks to run the kitten process, or to analyse, assess, reverse engineer, or security-test a piece of software for vulnerabilities — an installer, binary, container image, appliance, firmware, or application. Drives a repeatable 12-step vulnerability research workflow from obtaining the target through mapping attack surface, reverse engineering, finding high-impact vulnerabilities, building a proof-of-concept, and writing a vendor advisory. Every step is documented to a ...securitypythongoVotes: 0GitHub stars: 8