dotfiles-external-positioning

Check public repository commits for secret leaks and MIT license compliance.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/taloncjones/dotfiles --skill dotfiles-external-positioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotfiles-external-positioning
Source: https://github.com/taloncjones/dotfiles/tree/main/.claude/skills/dotfiles-external-positioning
Command: npx skills add https://github.com/taloncjones/dotfiles --skill dotfiles-external-positioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Ensures public-repo posture for sensitive and licensed code, providing safety checks and license enforcement.

Core Features & Use Cases

  • Publicrepo Posture: Defines and enforces what should not be committed into public repositories.
  • Security Checks: Implements multiple security layers to prevent accidental inclusion of secrets or sensitive information.
  • Licensing Compliance: Ensures MIT licensing adherence and manages third-party code inclusion and attribution.

Quick Start

Use the dotfiles-external-positioning skill to assess the safety of a commit and ensure licensing compliance before pushing to main.

Frequently Asked Questions about dotfiles-external-positioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent secrets and sensitive data from leaking into public repositories?

Public repo posture defines and enforces what should never be committed to public repositories. It applies to teams handling sensitive code, ensuring safety checks and license enforcement before pushing to main.

How do I enforce MIT license compliance for third-party code in my repository?

You can assess commit safety by running posture checks that scan for secret leaks, unauthorized dependencies, and license compliance. This skill provides security checks to evaluate code before pushing to main.

What is public repository posture and when do I need to enforce it?

Public repo posture defines and enforces what should never be committed to public repositories. It applies to teams handling sensitive code, ensuring safety checks and license enforcement before pushing to main.

Can I use this to check for unauthorized dependencies in shared code repositories?

Yes, checking for unauthorized dependencies is part of the security posture enforcement. This skill scans third-party code inclusion to prevent unauthorized dependencies from entering public repositories.

How do I assess commit safety and licensing before pushing to a public main branch?

Preventing secret leaks in public repositories requires enforcing posture checks before committing code. This skill implements multiple security layers to scan for sensitive information and prevent accidental inclusion in shared codebases.