askill
vastai-security-basics

vastai-security-basicsSafety 95Repository

Apply Vast.ai security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing Vast.ai security configuration. Trigger with phrases like "vastai security", "vastai secrets", "secure vastai", "vastai API key security".

48 stars
1.2k downloads
Updated 2/15/2026

Package Files

Loading files...
SKILL.md

Vast.ai Security Basics

Overview

Security best practices for Vast.ai API keys, tokens, and access control.

Prerequisites

  • Vast.ai SDK installed
  • Understanding of environment variables
  • Access to Vast.ai dashboard

Instructions

Step 1: Configure Environment Variables

# .env (NEVER commit to git)
VASTAI_API_KEY=sk_live_***
VASTAI_SECRET=***

# .gitignore
.env
.env.local
.env.*.local

Step 2: Implement Secret Rotation

# 1. Generate new key in Vast.ai dashboard
# 2. Update environment variable
export VASTAI_API_KEY="new_key_here"

# 3. Verify new key works
curl -H "Authorization: Bearer ${VASTAI_API_KEY}" \
  https://api.vastai.com/health

# 4. Revoke old key in dashboard

Step 3: Apply Least Privilege

EnvironmentRecommended Scopes
Developmentread:*
Stagingread:*, write:limited
ProductionOnly required scopes

Output

  • Secure API key storage
  • Environment-specific access controls
  • Audit logging enabled

Error Handling

Security IssueDetectionMitigation
Exposed API keyGit scanningRotate immediately
Excessive scopesAudit logsReduce permissions
Missing rotationKey age checkSchedule rotation

Examples

Service Account Pattern

const clients = {
  reader: new Vast.aiClient({
    apiKey: process.env.VASTAI_READ_KEY,
  }),
  writer: new Vast.aiClient({
    apiKey: process.env.VASTAI_WRITE_KEY,
  }),
};

Webhook Signature Verification

import crypto from 'crypto';

function verifyWebhookSignature(
  payload: string, signature: string, secret: string
): boolean {
  const expected = crypto.createHmac('sha256', secret).update(payload).digest('hex');
  return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}

Security Checklist

  • API keys in environment variables
  • .env files in .gitignore
  • Different keys for dev/staging/prod
  • Minimal scopes per environment
  • Webhook signatures validated
  • Audit logging enabled

Audit Logging

interface AuditEntry {
  timestamp: Date;
  action: string;
  userId: string;
  resource: string;
  result: 'success' | 'failure';
  metadata?: Record<string, any>;
}

async function auditLog(entry: Omit<AuditEntry, 'timestamp'>): Promise<void> {
  const log: AuditEntry = { ...entry, timestamp: new Date() };

  // Log to Vast.ai analytics
  await vastaiClient.track('audit', log);

  // Also log locally for compliance
  console.log('[AUDIT]', JSON.stringify(log));
}

// Usage
await auditLog({
  action: 'vastai.api.call',
  userId: currentUser.id,
  resource: '/v1/resource',
  result: 'success',
});

Resources

Next Steps

For production deployment, see vastai-prod-checklist.

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

95/100Analyzed 2/20/2026

High-quality security skill with excellent actionability, comprehensive coverage of API key management, secret rotation, least privilege access, and webhook verification. Well-structured with clear steps, code examples in TypeScript, tables for environment-specific scopes, and a security checklist. Includes proper metadata (version, license, author), clear trigger phrases, and tags for discoverability. The deep path (9 levels) is justified as it's in a test conformance directory for community plugins. No internal agent config detected.

95
95
90
95
95

Metadata

Licenseunknown
Version1.0.0
Updated2/15/2026
PublisherDicklesworthstone

Tags

apiobservabilitysecurity