Routes to local LLM for sensitive operations. Use when user says "로컬에서 처리해줘", "외부로 보내지 마", "민감한 데이터야", "보안 감사해줘", "credential 분석", "시크릿 확인", or handles sensitive data that should not leave the machine.
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: local-sensitive
description: Routes to local LLM for sensitive operations. Use when user says "로컬에서 처리해줘", "외부로 보내지 마", "민감한 데이터야", "보안 감사해줘", "credential 분석", "시크릿 확인", or handles sensitive data that should not leave the machine.
allowed-tools: Bash(.claude/scripts/local-llm.sh:*), Bash(.claude/scripts/infisical-update.sh:*), Bash(kubectl get:*), Read, Grep, Glob
---
# Local LLM for Sensitive Operations
Route security-sensitive tasks to local LLM to prevent data exfiltration.
## When to Use
- Analyzing secrets or credentials
- Security audit of sensitive code
- Private code review
- Compliance checking with sensitive data
- Any task where data should not leave the machine
## Available Models
| Model | Endpoint | Best For |
|-------|----------|----------|
| `qwen3-coder` | localhost:8003 | Code analysis, generation |
| `gpt-oss` | localhost:8004 | General tasks, tool use |
## How to Use
```bash
.claude/scripts/local-llm.sh qwen3-coder "Review this code for secrets: <code>"
.claude/scripts/local-llm.sh gpt-oss "Analyze security of this config"
```
## Security Guidelines
1. **Never** send sensitive data to external APIs
2. Use this skill when file paths contain: `secret`, `credential`, `.env`, `key`
3. Prefer `qwen3-coder` for code-related tasks
4. Prefer `gpt-oss` for general analysis
## Example Workflow
1. User asks: "Check if there are any hardcoded secrets in this file"
2. Read the file locally
3. Send to local LLM for analysis
4. Report findings without exposing actual secret values
## Infisical Secret Updates
For updating Infisical secrets with sensitive config data (token never exposed):
```bash
# 1. Parse sensitive YAML/JSON with local LLM
.claude/scripts/local-llm.sh qwen3-coder "Parse this config and output JSON: <config>"
# 2. Save to temp file
cat > /tmp/parsed.json << 'EOF'
{"KEY": "value"}
EOF
# 3. Safe update (token fetched internally, never printed)
.claude/scripts/infisical-update.sh safe-parse \
infisical-app-secrets namespace \
json /tmp/parsed.json "/path"
# 4. Clean up
rm /tmp/parsed.json
```
See `infisical-manager` skill for detailed workflow.
No comments yet. Be the first to comment!
Set up the Globalize CLI, create a translation project, and connect a GitHub or GitLab repository. Use this skill when the user asks to set up Globalize, install the Globalize CLI, authenticate with Globalize, or connect their project to the Globalize translation platform. Also use when the user mentions @globalize-now/cli-client or globalise-now-cli. This skill handles installation, authentication, project creation, and repository connection. For managing existing projects (glossaries, style...
Team Mode security research skill. Orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity by actual exploitability. Use for security review, vulnerability research, exploitability audit, pre-release security check, threat model validation, and `/security-research`. Triggers: 'security-research', 'security research', 'security review', 'vulnerability audit', 'exploitability audit', '보안 리뷰', '취...
Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.