[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQXZTTBQJZ4KA3546RVG78":3,"skill-same:01M7BQXZTTBQJZ4KA3546RVG78":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BQXZTTBQJZ4KA3546RVG78","env-secrets-manager",null,"Manage environment-variable hygiene and secrets safety across local development and production. Practical auditing, drift awareness, rotation readiness. Use when auditing .env files for committed secrets, planning a credential rotation, debugging missing-env-var production incidents, or hardening a new project against secrets leakage.","devlify-marketplace\u002Fdevlify-skills","devlify-marketplace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752365?v=4","01M7BPJC94F4G2AG0T3N220BQ3","Sadiq Abdullahi","01M7BPJC9QENFCHFM5NEFAJR1Y",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fenv-secrets-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"env-secrets-manager\"\ndescription: \"Manage environment-variable hygiene and secrets safety across local development and production. Practical auditing, drift awareness, rotation readiness. Use when auditing .env files for committed secrets, planning a credential rotation, debugging missing-env-var production incidents, or hardening a new project against secrets leakage.\"\n---\n\n# Env & Secrets Manager\n\n**Tier:** POWERFUL\n**Category:** Engineering\n**Domain:** Security \u002F DevOps \u002F Configuration Management\n\n---\n\n## Overview\n\nManage environment-variable hygiene and secrets safety across local development and production workflows. This skill focuses on practical auditing, drift awareness, and rotation readiness.\n\n## Core Capabilities\n\n- `.env` and `.env.example` lifecycle guidance\n- Secret leak detection for repository working trees\n- Severity-based findings for likely credentials\n- Operational pointers for rotation and containment\n- Integration-ready outputs for CI checks\n\n---\n\n## When to Use\n\n- Before pushing commits that touched env\u002Fconfig files\n- During security audits and incident triage\n- When onboarding contributors who need safe env conventions\n- When validating that no obvious secrets are hardcoded\n\n---\n\n## Quick Start\n\n```bash\n# Scan a repository for likely secret leaks\npython3 scripts\u002Fenv_auditor.py \u002Fpath\u002Fto\u002Frepo\n\n# JSON output for CI pipelines\npython3 scripts\u002Fenv_auditor.py \u002Fpath\u002Fto\u002Frepo --json\n```\n\n---\n\n## Recommended Workflow\n\n1. Run `scripts\u002Fenv_auditor.py` on the repository root.\n2. Prioritize `critical` and `high` findings first.\n3. Rotate real credentials and remove exposed values.\n4. Update `.env.example` and `.gitignore` as needed.\n5. Add or tighten pre-commit\u002FCI secret scanning gates.\n\n---\n\n## Reference Docs\n\n- `references\u002Fvalidation-detection-rotation.md`\n- `references\u002Fsecret-patterns.md`\n\n---\n\n## Common Pitfalls\n\n- Committing real values in `.env.example`\n- Rotating one system but missing downstream consumers\n- Logging secrets during debugging or incident response\n- Treating suspected leaks as low urgency without validation\n\n## Best Practices\n\n1. Use a secret manager as the production source of truth.\n2. Keep dev env files local and gitignored.\n3. Enforce detection in CI before merge.\n4. Re-test application paths immediately after credential rotation.\n\n---\n\n## Cloud Secret Store Integration\n\nProduction applications should never read secrets from `.env` files or environment variables baked into container images. Use a dedicated secret store instead.\n\n### Provider Comparison\n\n| Provider | Best For | Key Feature |\n|----------|----------|-------------|\n| **HashiCorp Vault** | Multi-cloud \u002F hybrid | Dynamic secrets, policy engine, pluggable backends |\n| **AWS Secrets Manager** | AWS-native workloads | Native Lambda\u002FECS\u002FEKS integration, automatic RDS rotation |\n| **Azure Key Vault** | Azure-native workloads | Managed HSM, Azure AD RBAC, certificate management |\n| **GCP Secret Manager** | GCP-native workloads | IAM-based access, automatic replication, versioning |\n\n### Selection Guidance\n\n- **Single cloud provider** — use the cloud-native secret manager. It integrates tightly with IAM, reduces operational overhead, and costs less than self-hosting.\n- **Multi-cloud or hybrid** — use HashiCorp Vault. It provides a uniform API across environments and supports dynamic secret generation (database credentials, cloud IAM keys) that expire automatically.\n- **Kubernetes-heavy** — combine External Secrets Operator with any backend above to sync secrets into K8s `Secret` objects without hardcoding.\n\n### Application Access Patterns\n\n1. **SDK\u002FAPI pull** — application fetches secret at startup or on-demand via provider SDK.\n2. **Sidecar injection** — a sidecar container (e.g., Vault Agent) writes secrets to a shared volume or injects them as environment variables.\n3. **Init container** — a Kubernetes init container fetches secrets before the main container starts.\n4. **CSI driver** — secrets mount as a filesystem volume via the Secrets Store CSI Driver.\n\n> **Cross-reference:** See `engineering\u002Fsecrets-vault-manager` for production vault infrastructure patterns, HA deployment, and disaster recovery procedures.\n\n---\n\n## Secret Rotation Workflow\n\nStale secrets are a liability. Rotation ensures that even if a credential leaks, its useful lifetime is bounded.\n\n### Phase 1: Detection\n\n- Track secret creation and expiry dates in your secret store metadata.\n- Set alerts at 30, 14, and 7 days before expiry.\n- Use `scripts\u002Fenv_auditor.py` to flag secrets with no recorded rotation date.\n\n### Phase 2: Rotation\n\n1. **Generate** a new credential (API key, database password, certificate).\n2. **Deploy** the new credential to all consumers (apps, services, pipelines) in parallel.\n3. **Verify** each consumer can authenticate using the new credential.\n4. **Revoke** the old credential only after all consumers are confirmed healthy.\n5. **Update** metadata with the new rotation timestamp and next rotation date.\n\n### Phase 3: Automation\n\n- **AWS Secrets Manager** — use built-in Lambda-based rotation for RDS, Redshift, and DocumentDB.\n- **HashiCorp Vault** — configure dynamic secrets with TTLs; credentials are generated on-demand and auto-expire.\n- **Azure Key Vault** — use Event Grid notifications to trigger rotation functions.\n- **GCP Secret Manager** — use Pub\u002FSub notifications tied to Cloud Functions for rotation logic.\n\n### Emergency Rotation Checklist\n\nWhen a secret is confirmed leaked:\n\n1. **Immediately revoke** the compromised credential at the provider level.\n2. Generate and deploy a replacement credential to all consumers.\n3. Audit access logs for unauthorized usage during the exposure window.\n4. Scan git history, CI logs, and artifact registries for the leaked value.\n5. File an incident report documenting scope, timeline, and remediation steps.\n6. Review and tighten detection controls to prevent recurrence.\n\n---\n\n## CI\u002FCD Secret Injection\n\nSecrets in CI\u002FCD pipelines require careful handling to avoid exposure in logs, artifacts, or pull request contexts.\n\n### GitHub Actions\n\n- Use **repository secrets** or **environment secrets** via `${{ secrets.SECRET_NAME }}`.\n- Prefer **OIDC federation** (`aws-actions\u002Fconfigure-aws-credentials` with `role-to-assume`) over long-lived access keys.\n- Environment secrets with required reviewers add approval gates for production deployments.\n- GitHub automatically masks secrets in logs, but avoid `echo` or `toJSON()` on secret values.\n\n### GitLab CI\n\n- Store secrets as **CI\u002FCD variables** with the `masked` and `protected` flags enabled.\n- Use **HashiCorp Vault integration** (`secrets:vault`) for dynamic secret injection without storing values in GitLab.\n- Scope variables to specific environments (`production`, `staging`) to enforce least privilege.\n\n### Universal Patterns\n\n- **Never echo or print** secret values in pipeline output, even for debugging.\n- **Use short-lived tokens** (OIDC, STS AssumeRole) instead of static credentials wherever possible.\n- **Restrict PR access** — do not expose secrets to pipelines triggered by forks or untrusted branches.\n- **Rotate CI secrets** on the same schedule as application secrets; pipeline credentials are attack vectors too.\n- **Audit pipeline logs** periodically for accidental secret exposure that masking may have missed.\n\n---\n\n## Pre-Commit Secret Detection\n\nCatching secrets before they reach version control is the most cost-effective defense. Two leading tools cover this space.\n\n### gitleaks\n\n```toml\n# .gitleaks.toml — minimal configuration\n[extend]\nuseDefault = true\n\n[[rules]]\nid = \"custom-internal-token\"\ndescription = \"Internal service token pattern\"\nregex = '''INTERNAL_TOKEN_[A-Za-z0-9]{32}'''\nsecretGroup = 0\n```\n\n- Install: `brew install gitleaks` or download from GitHub releases.\n- Pre-commit hook: `gitleaks git --pre-commit --staged`\n- Baseline scanning: `gitleaks detect --source . --report-path gitleaks-report.json`\n- Manage false positives in `.gitleaksignore` (one fingerprint per line).\n\n### detect-secrets\n\n```bash\n# Generate baseline\ndetect-secrets scan --all-files > .secrets.baseline\n\n# Pre-commit hook (via pre-commit framework)\n# .pre-commit-config.yaml\nrepos:\n  - repo: https:\u002F\u002Fgithub.com\u002FYelp\u002Fdetect-secrets\n    rev: v1.5.0\n    hooks:\n      - id: detect-secrets\n        args: ['--baseline', '.secrets.baseline']\n```\n\n- Supports **custom plugins** for organization-specific patterns.\n- Audit workflow: `detect-secrets audit .secrets.baseline` interactively marks true\u002Ffalse positives.\n\n### False Positive Management\n\n- Maintain `.gitleaksignore` or `.secrets.baseline` in version control so the whole team shares exclusions.\n- Review false positive lists during security audits — patterns may mask real leaks over time.\n- Prefer tightening regex patterns over broadly ignoring files.\n\n---\n\n## Audit Logging\n\nKnowing who accessed which secret and when is critical for incident investigation and compliance.\n\n### Cloud-Native Audit Trails\n\n| Provider | Service | What It Captures |\n|----------|---------|-----------------|\n| **AWS** | CloudTrail | Every `GetSecretValue`, `DescribeSecret`, `RotateSecret` API call |\n| **Azure** | Activity Log + Diagnostic Logs | Key Vault access events, including caller identity and IP |\n| **GCP** | Cloud Audit Logs | Data access logs for Secret Manager with principal and timestamp |\n| **Vault** | Audit Backend | Full request\u002Fresponse logging (file, syslog, or socket backend) |\n\n### Alerting Strategy\n\n- Alert on **access from unknown IP ranges** or service accounts outside the expected set.\n- Alert on **bulk secret reads** (more than N secrets accessed within a time window).\n- Alert on **access outside deployment windows** when no CI\u002FCD pipeline is running.\n- Feed audit logs into your SIEM (Splunk, Datadog, Elastic) for correlation with other security events.\n- Review audit logs quarterly as part of access recertification.\n\n---\n\n## Cross-References\n\nThis skill covers env hygiene and secret detection. For deeper coverage of related domains, see:\n\n| Skill | Path | Relationship |\n|-------|------|-------------|\n| **Secrets Vault Manager** | `engineering\u002Fsecrets-vault-manager` | Production vault infrastructure, HA deployment, DR |\n| **Senior SecOps** | `engineering\u002Fsenior-secops` | Security operations perspective, incident response |\n| **CI\u002FCD Pipeline Builder** | `engineering\u002Fci-cd-pipeline-builder` | Pipeline architecture, secret injection patterns |\n| **Infrastructure as Code** | `engineering\u002Finfrastructure-as-code` | Terraform\u002FPulumi secret backend configuration |\n| **Container Orchestration** | `engineering\u002Fcontainer-orchestration` | Kubernetes secret mounting, sealed secrets |\n","# Env & Secrets Manager\n\n**Tier:** POWERFUL\n**Category:** Engineering\n**Domain:** Security \u002F DevOps \u002F Configuration Management\n\n---\n\n## Overview\n\nManage environment-variable hygiene and secrets safety across local development and production workflows. This skill focuses on practical auditing, drift awareness, and rotation readiness.\n\n## Core Capabilities\n\n- `.env` and `.env.example` lifecycle guidance\n- Secret leak detection for repository working trees\n- Severity-based findings for likely credentials\n- Operational pointers for rotation and containment\n- Integration-ready outputs for CI checks\n\n---\n\n## When to Use\n\n- Before pushing commits that touched env\u002Fconfig files\n- During security audits and incident triage\n- When onboarding contributors who need safe env conventions\n- When validating that no obvious secrets are hardcoded\n\n---\n\n## Quick Start\n\n```bash\n# Scan a repository for likely secret leaks\npython3 scripts\u002Fenv_auditor.py \u002Fpath\u002Fto\u002Frepo\n\n# JSON output for CI pipelines\npython3 scripts\u002Fenv_auditor.py \u002Fpath\u002Fto\u002Frepo --json\n```\n\n---\n\n## Recommended Workflow\n\n1. Run `scripts\u002Fenv_auditor.py` on the repository root.\n2. Prioritize `critical` and `high` findings first.\n3. Rotate real credentials and remove exposed values.\n4. Update `.env.example` and `.gitignore` as needed.\n5. Add or tighten pre-commit\u002FCI secret scanning gates.\n\n---\n\n## Reference Docs\n\n- `references\u002Fvalidation-detection-rotation.md`\n- `references\u002Fsecret-patterns.md`\n\n---\n\n## Common Pitfalls\n\n- Committing real values in `.env.example`\n- Rotating one system but missing downstream consumers\n- Logging secrets during debugging or incident response\n- Treating suspected leaks as low urgency without validation\n\n## Best Practices\n\n1. Use a secret manager as the production source of truth.\n2. Keep dev env files local and gitignored.\n3. Enforce detection in CI before merge.\n4. Re-test application paths immediately after credential rotation.\n\n---\n\n## Cloud Secret Store Integration\n\nProduction applications should never read secrets from `.env` files or environment variables baked into container images. Use a dedicated secret store instead.\n\n### Provider Comparison\n\n| Provider | Best For | Key Feature |\n|----------|----------|-------------|\n| **HashiCorp Vault** | Multi-cloud \u002F hybrid | Dynamic secrets, policy engine, pluggable backends |\n| **AWS Secrets Manager** | AWS-native workloads | Native Lambda\u002FECS\u002FEKS integration, automatic RDS rotation |\n| **Azure Key Vault** | Azure-native workloads | Managed HSM, Azure AD RBAC, certificate management |\n| **GCP Secret Manager** | GCP-native workloads | IAM-based access, automatic replication, versioning |\n\n### Selection Guidance\n\n- **Single cloud provider** — use the cloud-native secret manager. It integrates tightly with IAM, reduces operational overhead, and costs less than self-hosting.\n- **Multi-cloud or hybrid** — use HashiCorp Vault. It provides a uniform API across environments and supports dynamic secret generation (database credentials, cloud IAM keys) that expire automatically.\n- **Kubernetes-heavy** — combine External Secrets Operator with any backend above to sync secrets into K8s `Secret` objects without hardcoding.\n\n### Application Access Patterns\n\n1. **SDK\u002FAPI pull** — application fetches secret at startup or on-demand via provider SDK.\n2. **Sidecar injection** — a sidecar container (e.g., Vault Agent) writes secrets to a shared volume or injects them as environment variables.\n3. **Init container** — a Kubernetes init container fetches secrets before the main container starts.\n4. **CSI driver** — secrets mount as a filesystem volume via the Secrets Store CSI Driver.\n\n> **Cross-reference:** See `engineering\u002Fsecrets-vault-manager` for production vault infrastructure patterns, HA deployment, and disaster recovery procedures.\n\n---\n\n## Secret Rotation Workflow\n\nStale secrets are a liability. Rotation ensures that even if a credential leaks, its useful lifetime is bounded.\n\n### Phase 1: Detection\n\n- Track secret creation and expiry dates in your secret store metadata.\n- Set alerts at 30, 14, and 7 days before expiry.\n- Use `scripts\u002Fenv_auditor.py` to flag secrets with no recorded rotation date.\n\n### Phase 2: Rotation\n\n1. **Generate** a new credential (API key, database password, certificate).\n2. **Deploy** the new credential to all consumers (apps, services, pipelines) in parallel.\n3. **Verify** each consumer can authenticate using the new credential.\n4. **Revoke** the old credential only after all consumers are confirmed healthy.\n5. **Update** metadata with the new rotation timestamp and next rotation date.\n\n### Phase 3: Automation\n\n- **AWS Secrets Manager** — use built-in Lambda-based rotation for RDS, Redshift, and DocumentDB.\n- **HashiCorp Vault** — configure dynamic secrets with TTLs; credentials are generated on-demand and auto-expire.\n- **Azure Key Vault** — use Event Grid notifications to trigger rotation functions.\n- **GCP Secret Manager** — use Pub\u002FSub notifications tied to Cloud Functions for rotation logic.\n\n### Emergency Rotation Checklist\n\nWhen a secret is confirmed leaked:\n\n1. **Immediately revoke** the compromised credential at the provider level.\n2. Generate and deploy a replacement credential to all consumers.\n3. Audit access logs for unauthorized usage during the exposure window.\n4. Scan git history, CI logs, and artifact registries for the leaked value.\n5. File an incident report documenting scope, timeline, and remediation steps.\n6. Review and tighten detection controls to prevent recurrence.\n\n---\n\n## CI\u002FCD Secret Injection\n\nSecrets in CI\u002FCD pipelines require careful handling to avoid exposure in logs, artifacts, or pull request contexts.\n\n### GitHub Actions\n\n- Use **repository secrets** or **environment secrets** via `${{ secrets.SECRET_NAME }}`.\n- Prefer **OIDC federation** (`aws-actions\u002Fconfigure-aws-credentials` with `role-to-assume`) over long-lived access keys.\n- Environment secrets with required reviewers add approval gates for production deployments.\n- GitHub automatically masks secrets in logs, but avoid `echo` or `toJSON()` on secret values.\n\n### GitLab CI\n\n- Store secrets as **CI\u002FCD variables** with the `masked` and `protected` flags enabled.\n- Use **HashiCorp Vault integration** (`secrets:vault`) for dynamic secret injection without storing values in GitLab.\n- Scope variables to specific environments (`production`, `staging`) to enforce least privilege.\n\n### Universal Patterns\n\n- **Never echo or print** secret values in pipeline output, even for debugging.\n- **Use short-lived tokens** (OIDC, STS AssumeRole) instead of static credentials wherever possible.\n- **Restrict PR access** — do not expose secrets to pipelines triggered by forks or untrusted branches.\n- **Rotate CI secrets** on the same schedule as application secrets; pipeline credentials are attack vectors too.\n- **Audit pipeline logs** periodically for accidental secret exposure that masking may have missed.\n\n---\n\n## Pre-Commit Secret Detection\n\nCatching secrets before they reach version control is the most cost-effective defense. Two leading tools cover this space.\n\n### gitleaks\n\n```toml\n# .gitleaks.toml — minimal configuration\n[extend]\nuseDefault = true\n\n[[rules]]\nid = \"custom-internal-token\"\ndescription = \"Internal service token pattern\"\nregex = '''INTERNAL_TOKEN_[A-Za-z0-9]{32}'''\nsecretGroup = 0\n```\n\n- Install: `brew install gitleaks` or download from GitHub releases.\n- Pre-commit hook: `gitleaks git --pre-commit --staged`\n- Baseline scanning: `gitleaks detect --source . --report-path gitleaks-report.json`\n- Manage false positives in `.gitleaksignore` (one fingerprint per line).\n\n### detect-secrets\n\n```bash\n# Generate baseline\ndetect-secrets scan --all-files > .secrets.baseline\n\n# Pre-commit hook (via pre-commit framework)\n# .pre-commit-config.yaml\nrepos:\n  - repo: https:\u002F\u002Fgithub.com\u002FYelp\u002Fdetect-secrets\n    rev: v1.5.0\n    hooks:\n      - id: detect-secrets\n        args: ['--baseline', '.secrets.baseline']\n```\n\n- Supports **custom plugins** for organization-specific patterns.\n- Audit workflow: `detect-secrets audit .secrets.baseline` interactively marks true\u002Ffalse positives.\n\n### False Positive Management\n\n- Maintain `.gitleaksignore` or `.secrets.baseline` in version control so the whole team shares exclusions.\n- Review false positive lists during security audits — patterns may mask real leaks over time.\n- Prefer tightening regex patterns over broadly ignoring files.\n\n---\n\n## Audit Logging\n\nKnowing who accessed which secret and when is critical for incident investigation and compliance.\n\n### Cloud-Native Audit Trails\n\n| Provider | Service | What It Captures |\n|----------|---------|-----------------|\n| **AWS** | CloudTrail | Every `GetSecretValue`, `DescribeSecret`, `RotateSecret` API call |\n| **Azure** | Activity Log + Diagnostic Logs | Key Vault access events, including caller identity and IP |\n| **GCP** | Cloud Audit Logs | Data access logs for Secret Manager with principal and timestamp |\n| **Vault** | Audit Backend | Full request\u002Fresponse logging (file, syslog, or socket backend) |\n\n### Alerting Strategy\n\n- Alert on **access from unknown IP ranges** or service accounts outside the expected set.\n- Alert on **bulk secret reads** (more than N secrets accessed within a time window).\n- Alert on **access outside deployment windows** when no CI\u002FCD pipeline is running.\n- Feed audit logs into your SIEM (Splunk, Datadog, Elastic) for correlation with other security events.\n- Review audit logs quarterly as part of access recertification.\n\n---\n\n## Cross-References\n\nThis skill covers env hygiene and secret detection. For deeper coverage of related domains, see:\n\n| Skill | Path | Relationship |\n|-------|------|-------------|\n| **Secrets Vault Manager** | `engineering\u002Fsecrets-vault-manager` | Production vault infrastructure, HA deployment, DR |\n| **Senior SecOps** | `engineering\u002Fsenior-secops` | Security operations perspective, incident response |\n| **CI\u002FCD Pipeline Builder** | `engineering\u002Fci-cd-pipeline-builder` | Pipeline architecture, secret injection patterns |\n| **Infrastructure as Code** | `engineering\u002Finfrastructure-as-code` | Terraform\u002FPulumi secret backend configuration |\n| **Container Orchestration** | `engineering\u002Fcontainer-orchestration` | Kubernetes secret mounting, sealed secrets |\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","engineering\u002Fskills\u002Fenv-secrets-manager",0,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace","devlify.com.ng","Software Developer & full-stack dev building secure web and mobile applications, AI\u002FML solutions, and scalable digital products. Founder of Devlify ","2026-08-30 00:40:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add devlify-marketplace\u002Fdevlify-skills --skill env-secrets-manager",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill env-secrets-manager",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill env-secrets-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fenv-secrets-manager\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsecret-patterns.md","REFERENCE","参考文档",1140,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fenv-secrets-manager\u002Freferences\u002Fsecret-patterns.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fvalidation-detection-rotation.md",9457,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fenv-secrets-manager\u002Freferences\u002Fvalidation-detection-rotation.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fenv_auditor.py","SCRIPT","脚本",4482,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fenv-secrets-manager\u002Fscripts\u002Fenv_auditor.py",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7BRV5Q3BJT22HG25WJFTKZN","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7BRTW6RRTHXT6SBE41AY5GD","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research, deepread for evidence-first reading of supplied documents) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7BRTMK3PGPNH76R2HY57AKC","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7BRTAR0YJWNZ2AP3QTH39BW","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7BRT3J0V5A9V3VJ96G97AGW","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7BRSS7P0CJP7X9ERDFYN6GC","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]