Back to catalog
Static reviewDevelopment

Skill dossier

implementing-api-key-security-controls

Source declaration

Implements secure API key generation with sufficient entropy, server-side hashing (SHA-256/bcrypt) instead of plaintext storage, per-key scoping to endpoints/IPs/rate limits, zero-downtime rotation, and automated leak monitoring across GitHub repos, logs, and client-side code. Use when designing API key formats, building key rotation or revocation workflows, or protecting server-to-server API credentials from leakage, brute force, and abuse.

The author's original description, preserved in English. It describes intent, not verified performance.

Implements secure API key generation with sufficient entropy, server-side hashing (SHA-256/bcrypt) instead of plaintext storage, per-key scoping to endpoints/IPs/rate limits, zero-downtime rotation, and automated leak monitoring across GitHub repos, logs, and client-side code. Use when designing API key formats, building key rotation or revocation workflows, or protecting server-to-server API credentials from leakage, brute force, and abuse.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Implements secure API key generation with sufficient entropy, server-side hashing (SHA-256/bcrypt) instead of plaintext storage, per-key scoping to endpoints/IPs/rate limits, zero-downtime rotation, and automated leak monitoring across GitHub repos, logs, and client-side code. Use when designing API key formats, building key rotation or revocation workflows, or protecting server-to-server API credentials from leakage, brute force, and abuse. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-api-key-security-controls/SKILL.md:L60]
  • Step 1: Secure API Key Generation [Source statement; provisional, not tested. Evidence: skills/implementing-api-key-security-controls/SKILL.md:L62]
  • Step 2: API Key Validation Middleware [Source statement; provisional, not tested. Evidence: skills/implementing-api-key-security-controls/SKILL.md:L234]
  • Step 3: Automated Key Leakage Detection [Source statement; provisional, not tested. Evidence: skills/implementing-api-key-security-controls/SKILL.md:L292]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-api-key-security-controls/SKILL.md:L1-L39]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-api-key-security-controls/LICENSEOther11 KB
skills/implementing-api-key-security-controls/references/api-reference.mdReference1.3 KB
skills/implementing-api-key-security-controls/scripts/agent.pyScript5.9 KB
skills/implementing-api-key-security-controls/SKILL.mdInstruction15.4 KB

SKILL.md frontmatter

{
  "name": "implementing-api-key-security-controls",
  "description": "Implements secure API key generation with sufficient entropy, server-side hashing (SHA-256/bcrypt) instead of plaintext storage, per-key scoping to endpoints/IPs/rate limits, zero-downtime rotation, and automated leak monitoring across GitHub repos, logs, and client-side code. Use when designing API key formats, building key rotation or revocation workflows, or protecting server-to-server API credentials from leakage, brute force, and abuse.",
  "domain": "cybersecurity",
  "subdomain": "api-security",
  "tags": [
    "api-security",
    "api-keys",
    "credential-management",
    "key-rotation",
    "secret-management"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MAP-5.1",
    "MANAGE-2.4"
  ],
  "atlas_techniques": [
    "AML.T0070",
    "AML.T0066",
    "AML.T0082"
  ],
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1552.001",
    "T1003",
    "T1110"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Secure API Key Generation

    Source-described action candidate under “Step 1: Secure API Key Generation”; not verified execution.

  4. 04
    Action

    Step 2: API Key Validation Middleware

    Source-described action candidate under “Step 2: API Key Validation Middleware”; not verified execution.

  5. 05
    Action

    Step 3: Automated Key Leakage Detection

    Source-described action candidate under “Step 3: Automated Key Leakage Detection”; not verified execution.

  6. 06
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

Inspect all extracted workflow candidates (17 candidate steps)
  1. 07
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  2. 08
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  3. 09
    Action

    Implement prefixed API keys (sklive, sktest) with 256-bit entropy for leak detection

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  4. 10
    Action

    Store only SHA-256 hashes of keys in the database, cache validated keys in Redis

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  5. 11
    Action

    Implement per-key scoping: each key restricted to specific endpoints, rate limits, and optional IP allowlists

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  6. 12
    Action

    Build key rotation API with 24-hour grace period for seamless transitions

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  7. 13
    Action

    Integrate with GitHub Secret Scanning to automatically detect and revoke leaked keys within minutes

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  8. 14
    Action

    Run gitleaks in CI/CD pipelines to prevent key commits in first place

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  9. 15
    Action

    Implement anomaly detection: alert on keys used from unusual IPs or with abnormal traffic patterns

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  10. 16
    Action

    Add key expiration policy: all keys expire after 365 days with 30-day advance notification

    Source-described action candidate under “Scenario: API Key Security Program for Developer Platform”; not verified execution.

  11. 17
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

26 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

8 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

11 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

7 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-api-key-security-controls/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/implementing-api-key-security-controls/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-api-key-security-controls
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.