AGENT SKILL

validating-authentication-implementations

This skill enables Claude to validate authentication implementations against security best practices and industry standards. It analyzes various authentication methods, including JWT, OAuth, session-based authentication, and API keys. Use this skill when you need to perform an authentication security check, assess password policies, evaluate MFA implementation, or analyze session security. Trigger this skill with phrases like "validate authentication," "authentication check," or "authcheck."

License 许可
MIT
最近更新
2026-11-11
Stars
★ 2
Forks
0

01 前言 Front Matter

name
validating-authentication-implementations
description
This skill enables Claude to validate authentication implementations against security best practices and industry standards. It analyzes various authentication methods, including JWT, OAuth, session-based authentication, and API keys. Use this skill when you need to perform an authentication security check, assess password policies, evaluate MFA implementation, or analyze session security. Trigger this skill with phrases like "validate authentication," "authentication check," or "authcheck."

02 资源文件 3

03 SKILL.md 正文

Overview

This skill allows Claude to assess the security of authentication mechanisms in a system or application. It provides a detailed report highlighting potential vulnerabilities and offering recommendations for improvement based on established security principles.

How It Works

  1. Initiate Validation: Upon receiving a trigger phrase, the skill activates the authentication-validator plugin.
  2. Analyze Authentication Methods: The plugin examines the implemented authentication methods, such as JWT, OAuth, session-based, or API keys.
  3. Generate Security Report: The plugin generates a comprehensive report outlining potential vulnerabilities and recommended fixes related to password security, session management, token security (JWT), multi-factor authentication, and account security.

When to Use This Skill

This skill activates when you need to:

  • Assess the security of an application's authentication implementation.
  • Identify vulnerabilities in password policies and session management.
  • Evaluate the security of JWT tokens and MFA implementation.
  • Ensure compliance with security best practices and industry standards.

Examples

Example 1: Assessing JWT Security

User request: "validate authentication for jwt implementation"

The skill will:

  1. Activate the authentication-validator plugin.
  2. Analyze the JWT implementation, checking for strong signing algorithms, proper expiration claims, and audience/issuer validation.
  3. Generate a report highlighting any vulnerabilities and recommending best practices for JWT security.

Example 2: Checking Session Security

User request: "authcheck session cookies"

The skill will:

  1. Activate the authentication-validator plugin.
  2. Analyze the session cookie settings, including HttpOnly, Secure, and SameSite attributes.
  3. Generate a report outlining any potential session fixation or CSRF vulnerabilities and recommending appropriate countermeasures.

Best Practices

  • Password Hashing: Always use strong hashing algorithms like bcrypt or Argon2 with appropriate salt generation.
  • Token Expiration: Implement short-lived access tokens and refresh token rotation for enhanced security.
  • Multi-Factor Authentication: Encourage or enforce MFA to mitigate the risk of password compromise.

Integration

This skill can be used in conjunction with other security-related plugins to provide a comprehensive security assessment of an application. For example, it can be used alongside a code analysis plugin to identify potential code-level vulnerabilities related to authentication.

04 同仓库更多 Skills

sandraschi
sandraschi/documentation-mcp

Docs Research

Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).

资料检索与研究Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

wrappee-drift

Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.

★ 2
sandraschi
sandraschi/documentation-mcp

modules

暂无简介

运维与部署Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

mcp-standards

Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.

测试与质量Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

webapp-cua-test

Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).

测试与质量Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

ship

Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.

Skill与智能体开发
★ 2