Skip to content
Rapid Response Procedures

Takedown & Security Policy

We take ecosystem safety seriously. Whether you discovered malicious code, need to submit a formal copyright notice, or simply wish to opt out your repository, our response channels and guaranteed SLAs are detailed below.

Stream 1: Critical Security / Malware
< 12 Hours SLA

For backdoors, credential harvesters, prompt injection exploits, or network egress attacks.

Stream 2: DMCA & Copyright Notices
< 48 Hours SLA

For formal copyright infringement claims, trademark disputes, or licensing issues.

1. Emergency Security & Malicious Code Reporting

Because AI agent skills instruct local execution environments, any repository containing active malicious payloads represents an urgent threat. We treat security reports with the highest priority.

What qualifies for immediate emergency delisting:

  • Credential or Key Theft: Scripts reading ~/.ssh, ~/.aws, .env, or environment variables and sending them to an external endpoint.
  • Unauthorized Remote Execution: Code silently pulling arbitrary binaries (curl ... | bash) or launching hidden background listener processes.
  • Malicious Prompt Injections: Instructions structured to force the agent to hide its operations, bypass user confirmation prompts, or manipulate private files.
  • Destructive Filesystem Traversal: Scripts attempting directory escapes or recursive file deletions outside designated project workspaces.
How to submit an emergency report:

Email [email protected] with the subject line format:
[SECURITY URGENT] <Skill Name or Repository URL>

Please include:

  • URL of the listing on vibeskills.dev and source repository commit SHA.
  • Specific file and line numbers containing the malicious behavior.
  • A short technical explanation or proof-of-concept (PoC).

2. Copyright Infringement & DMCA Takedown Procedure

vibeskills.dev complies with the Digital Millennium Copyright Act (17 U.S.C. § 512) and applicable intellectual property laws. If you believe your copyrighted work has been cataloged without authorization in violation of open-source license provisions, you may submit a formal notification.

Required elements for a DMCA Notice:

  1. A physical or electronic signature of the copyright owner or authorized representative.
  2. Identification of the copyrighted work claimed to have been infringed (e.g. your original repository link).
  3. Identification of the material claimed to be infringing on vibeskills.dev (the exact skill URL).
  4. Your contact information (name, mailing address, telephone number, and email address).
  5. A statement that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law.
  6. A statement, made under penalty of perjury, that the information in your notice is accurate and that you are authorized to act on behalf of the owner.
Send formal notices to: [email protected]

3. Author Self-Opt-Out (Zero Friction)

You do not need to issue a legal notice if you simply want your repository excluded from our index. We respect developer sovereignty and provide two simple ways to opt out:

Method A: Repository File (.skillsindexignore)

Add an empty file or configuration named .skillsindexignore in the root of your GitHub repository. The crawler reads this on its next pass, marks the repository as opted-out, and deletes all metadata records.

Method B: Email Request

Send an email from the address associated with your GitHub profile to [email protected] stating that you would like your repository removed. We process these within 24 hours.

4. Counter-Notice & False Report Appeals

If your skill was flagged or delisted due to a mistaken security finding or an invalid copyright claim, you can submit a counter-notice or security dispute. Include the original listing URL, an explanation clarifying the benign intent of flagged code blocks, and any verification tests. Our technical review team evaluates appeals within 48 business hours.

Common Questions

Takedown FAQs

Does delisting on vibeskills.dev remove the file from GitHub?

No. vibeskills.dev only removes the listing and metadata from our own search directory and API. To remove content from GitHub, you must contact GitHub Trust & Safety directly.

Will delisting affect my repository's GitHub status or stars?

Not at all. vibeskills.dev has zero control over GitHub or your source repository. It only stops vibeskills.dev from displaying your skill to our users.

Search directory

Try a search