Claude Skill

authentication-testing

Use this skill when you need evidence-bounded authentication-testing analysis and validation preparation; triggers include 身份认证测试 and authentication-testing.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download naodeng-awesome-qa-skills-skills_en_testing-types_authentication-testing-9df700b.zip · 8 KB

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/authentication-testing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
Git git clone https://github.com/naodeng/awesome-qa-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Authentication Testing

When to Use

  • Use this Skill when the work needs evidence-bounded analysis of identity credentials, authentication flows, failure paths, and lifecycle.
  • Use it when input is incomplete but a reviewable draft with assumptions and gaps is still useful.
  • Use it when static security evidence must remain separate from planned validation and completed execution.

Output Format Options

  • Default to Markdown organized by security risk, evidence, and priority.
  • If the user asks for a table, CSV, JSON, or ticket format, preserve the same finding fields and evidence states.
  • Confirm the schema, enum values, and required fields before feeding the output to automation.

How to Use

  1. Read prompts/authentication-testing.md and follow its input audit, coverage checklist, and output contract.
  2. Extract scope, environment, version, roles, data, dependencies, constraints, and available evidence.
  3. Model identity credentials, authentication flows, failure paths, and lifecycle with reviewable scenarios, separating known facts, inferences, and candidate validation.
  4. Record impact, priority, owner role, close condition, and validation method for each item.
  5. With incomplete input, deliver a bounded draft; do not turn a risk assumption into a confirmed vulnerability or security pass.

Reference Files

  • Read prompts/authentication-testing.md for every invocation.
  • Read evals/eval.yaml and matching evals/cases/ when evaluating the Skill.
  • Read references/, examples/, scripts/, or output-formats.md only when the directory exists and the task needs it.

Domain Execution Essentials

  • Model unauthenticated, challenged, authenticated, locked and recovery states for supplied password/MFA/recovery/federation mechanisms, with creation/rotation/expiry/revocation/replay rules.
  • Deliver authentication transitions and credential lifecycles with expected state/token, observation and gaps; authentication does not replace authorization.
  • When deriving domain candidates, read and follow prompts/authentication-testing.md for the domain procedure and oracle; retain valid controls, evidence gaps, and validation actions for each item.

Core Constraints

  • Analyze only identity credentials, authentication flows, failure paths, and lifecycle; do not log in, call real APIs, or read credentials.
  • Do not invent vulnerabilities, exploit success, remediation completion, scan coverage, or security-pass claims.
  • Mark unsupported evidence as pending, blocked, or unassessed and provide an isolated validation method.
  • Leave risk acceptance, exception authorization, and release judgment to a Human.

Delivery Self-Check

  • Complete the known, missing, conflicting, stale, out_of_scope, and assumptions audit.
  • Cover the authentication, triggers, expected concerns, and evidence state.
  • Separate facts, inferences, recommendations, gaps, and Human decisions.
  • Do not turn static findings or a dry-run into a real exploit, absence-of-vulnerability, or release-approval claim.

Common Pitfalls

  • Treating broad security review or API contract checking as a complete substitute for Authentication Testing.
  • Listing attack names without applicability, evidence, expected results, or close conditions.
  • Declaring a system secure with incomplete input, or reading real credentials for completeness.

Best Practices

  • Start with high-impact, hard-to-detect, permission-sensitive, or data-sensitive paths.
  • Use redacted material, least privilege, isolated environments, and reversible validation suggestions.
  • Make each security conclusion reviewable by another engineer from its source and boundary.
Files (awesome-qa-skills)
  • agents
    • openai.yaml 332 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 1.3 KB
        Loading…
      • domain-method-control.yaml 1.5 KB
        Loading…
      • domain-method-success.yaml 1.4 KB
        Loading…
      • edge-incomplete-input.yaml 803 B
        Loading…
      • edge-scope-boundary.yaml 890 B
        Loading…
    • eval.yaml 531 B
      Loading…
    • local-rules.json 141 B
      Loading…
    • trigger-prompts.csv 445 B · in bundle
  • prompts
    • authentication-testing.md 5 KB
      Loading…
  • SKILL.md 4.1 KB
    ---
    name: authentication-testing
    description: Use this skill when you need evidence-bounded authentication-testing analysis and validation preparation; triggers include 身份认证测试 and authentication-testing.
    license: PolyForm-Noncommercial-1.0.0
    metadata:
      version: "1.0.0"
      compatibility: ""
      author: "Awesome QA Skills contributors"
      language: "en"
      category: "testing-types"
      source: "https://github.com/naodeng/awesome-qa-skills"
      license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
    ---
    
    # Authentication Testing
    
    ## When to Use
    
    - Use this Skill when the work needs evidence-bounded analysis of identity credentials, authentication flows, failure paths, and lifecycle.
    - Use it when input is incomplete but a reviewable draft with assumptions and gaps is still useful.
    - Use it when static security evidence must remain separate from planned validation and completed execution.
    
    ## Output Format Options
    
    - Default to Markdown organized by security risk, evidence, and priority.
    - If the user asks for a table, CSV, JSON, or ticket format, preserve the same finding fields and evidence states.
    - Confirm the schema, enum values, and required fields before feeding the output to automation.
    
    ## How to Use
    
    1. Read prompts/authentication-testing.md and follow its input audit, coverage checklist, and output contract.
    2. Extract scope, environment, version, roles, data, dependencies, constraints, and available evidence.
    3. Model identity credentials, authentication flows, failure paths, and lifecycle with reviewable scenarios, separating known facts, inferences, and candidate validation.
    4. Record impact, priority, owner role, close condition, and validation method for each item.
    5. With incomplete input, deliver a bounded draft; do not turn a risk assumption into a confirmed vulnerability or security pass.
    
    ## Reference Files
    
    - Read prompts/authentication-testing.md for every invocation.
    - Read evals/eval.yaml and matching evals/cases/ when evaluating the Skill.
    - Read references/, examples/, scripts/, or output-formats.md only when the directory exists and the task needs it.
    
    ## Domain Execution Essentials
    
    - Model unauthenticated, challenged, authenticated, locked and recovery states for supplied password/MFA/recovery/federation mechanisms, with creation/rotation/expiry/revocation/replay rules.
    - Deliver authentication transitions and credential lifecycles with expected state/token, observation and gaps; authentication does not replace authorization.
    - When deriving domain candidates, read and follow [prompts/authentication-testing.md](prompts/authentication-testing.md) for the domain procedure and oracle; retain valid controls, evidence gaps, and validation actions for each item.
    
    ## Core Constraints
    
    - Analyze only identity credentials, authentication flows, failure paths, and lifecycle; do not log in, call real APIs, or read credentials.
    - Do not invent vulnerabilities, exploit success, remediation completion, scan coverage, or security-pass claims.
    - Mark unsupported evidence as pending, blocked, or unassessed and provide an isolated validation method.
    - Leave risk acceptance, exception authorization, and release judgment to a Human.
    
    ## Delivery Self-Check
    
    - [ ] Complete the known, missing, conflicting, stale, out_of_scope, and assumptions audit.
    - [ ] Cover the authentication, triggers, expected concerns, and evidence state.
    - [ ] Separate facts, inferences, recommendations, gaps, and Human decisions.
    - [ ] Do not turn static findings or a dry-run into a real exploit, absence-of-vulnerability, or release-approval claim.
    
    ## Common Pitfalls
    
    - Treating broad security review or API contract checking as a complete substitute for Authentication Testing.
    - Listing attack names without applicability, evidence, expected results, or close conditions.
    - Declaring a system secure with incomplete input, or reading real credentials for completeness.
    
    ## Best Practices
    
    - Start with high-impact, hard-to-detect, permission-sensitive, or data-sensitive paths.
    - Use redacted material, least privilege, isolated environments, and reversible validation suggestions.
    - Make each security conclusion reviewable by another engineer from its source and boundary.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.