DMCA Safe Harbor & Intellectual Property Policy

1. Scope and verified status

This policy covers skills-si.com listings, stored readmes, ZIP downloads, repository submissions and the platform's own pages. Most current entries were independently imported by the platform from public GitHub repositories, not uploaded anonymously by users. General intellectual-property contact: Drew@skills-si.com and /copyright. A receipt is not a finding of infringement, removal confirmation or legal immunity.

The operator's full legal name and physical address, the designated agent's name, mailing address and telephone number, an active U.S. Copyright Office designation and its renewal date have not been supplied or verified. We therefore do not claim a registered DMCA agent or established safe-harbor eligibility. The email is currently a general contact, not automatically a registered agent. Statutory procedures below apply where U.S. law and the necessary conditions apply; the owner must confirm the details and obtain legal review.

2. Conditional safe harbors, not permission or immunity from suit

Section 512 of the U.S. Digital Millennium Copyright Act limits monetary copyright liability for specified activities of qualifying providers and permits certain injunctions. It is not a license or a universal shield against lawsuits. Failure to qualify is not itself proof of infringement; liability depends on the facts and law. [1][2]

Section 512 distinguishes conduits, caching, user-directed storage and information-location tools. Original-source links may raise §512(d); genuinely user-directed hosting may raise §512(c). The platform's own selection, copying and redistribution cannot simply be relabeled user-directed storage because its source is public. Nor should independent mirrors be assumed to meet §512(b) caching conditions. A host's status, attribution or disclaimer does not substitute for this operator's permissions and activity-specific analysis. [1][2]

Other jurisdictions' copyright, trademark, privacy and platform laws may apply. This page selects no general forum, imposes no U.S. jurisdiction on ordinary visitors, and claims no global immunity.

3. Conditions the owner must actually satisfy

For activities seeking §512(c) or (d) protection, assess actual or red-flag knowledge; expeditious removal upon obtaining such knowledge or an adequate notice; no direct financial benefit from infringement where the provider has the right and ability to control it; agent designation, applicable registration and public contact details; a reasonably implemented repeat-infringer policy; and accommodation without interference with qualifying standard technical measures. Registration alone does not establish eligibility. [1][2]

Section 512(m) generally does not condition protection on monitoring the entire service, but does not permit ignoring known infringement, apparent facts or valid notices. Independent imports still need their own licensing review.

4. Agent designation, publication and renewal

If the owner elects to pursue the applicable safe harbor, use the real operating legal entity in the Copyright Office's electronic directory. Separate entities need separate designations. Supply the provider's legal name, physical street address and alternate names/domain, and the agent's name, organization, mailing address, phone and email. Publicly publish agent contact information. Manus and the registrar are not automatically this site's agents. [3]

A designation generally expires three years after registration or its last renewal; an amendment or resubmission resets the period. Maintain current contact information and calendar the actual renewal date. A website email or policy is not registration. No registration, payment or sworn filing is made through publication of this page. Unverified names, addresses or registration numbers must not be invented. [3]

5. Licensing and redistribution review

Rights in code, instructions, images, fonts and documents belong to their actual holders; a repository author may not own every asset. Public access, free downloads and GitHub fork availability are not general permission to copy, modify, commercialize or redistribute. Without a license, do not assume permission to distribute. Links do not excuse ignoring known infringement. [4]

Retain source/file URLs, commit or release, import date, exact license and scope, submitting source and authorization evidence. File- or directory-specific conditions and third-party asset licenses may differ from the repository-root label. Retain attribution, LICENSE and NOTICE and comply with applicable redistribution duties. Pause unclear, conflicting or restrictive permissions for professional review; automated detection is not legal advice.

Submitters must be entitled to share links and descriptions; files proposed for storage or distribution need permission. The platform's brand and arrangement do not alter third-party rights. No official relationship with GitHub, SkillsMP, Anthropic, OpenAI or skill authors is implied. AI generation or translation does not necessarily remove underlying rights.

6. Elements of a statutory DMCA notice

A written §512(c)(3) notice to the designated agent must substantially include: (1) a physical or electronic signature of an authorized person; (2) identification of the protected work or a representative list for multiple works at one site; (3) identification and locating information for the material to remove or disable, or the affected reference/link; (4) sufficient complainant contact information, such as address, phone and available email; (5) a good-faith belief that the complained-of use is not authorized by the owner, agent or law; and (6) accuracy and, under penalty of perjury, authority to act for the owner of the allegedly infringed exclusive right. [1][2]

Use a subject such as 'DMCA Notice — listing ID/URL' and the verified published agent channel. Pending designation, contact the general mailbox without treating a web receipt as proof all statutory elements are met. The current online form is an initial/general report: its rights confirmation does not include every statutory signature, statement and contact field. Further materials may be needed.

Consider permission and uses allowed by law, including applicable fair use. Where a deficient notice substantially identifies the work, material and contact, promptly seek supplementation as required; do not mechanically disregard independent knowledge of infringement.

7. Intake, expeditious action and all public copies

Assign an actual person to monitor inbox and spam, record references, receipt times, sources, affected entries, evidence and decisions. A notice is not a final judicial determination. Assess locating information and applicable substantial compliance. Act expeditiously on valid notices or actual/red-flag knowledge; do not wait for multiple complaints or demand a court judgment in every case. Suspend disputed access where necessary while resolving the issue.

Removal must address listings/search, readme snapshots, APIs, direct static ZIP URLs, exported JSON, sitemaps, object storage and public cache copies. Removing a button alone is insufficient. Record stable IDs, repository/path or hashes to prevent reimport; retained evidence must not remain publicly downloadable. Verify old addresses after deployment.

Where §512(g) applies, take reasonable steps promptly to notify the affected subscriber of removal. For independently imported material with no uploading subscriber, record that fact rather than invent one. Contact the source where appropriate, explain actual actions and remedies, and do not claim to erase all Internet copies.

8. Counter-notices, jurisdiction and 10–14 business days

A §512(g)(3) counter-notice includes the subscriber's physical/electronic signature; the removed material and prior location; a statement under penalty of perjury of good-faith belief in mistake or misidentification; name, address and telephone; consent to the Federal District Court for the district of that address, or, outside the United States, any judicial district where the provider may be found; and acceptance of service from the original notifier or agent. [1][2]

These jurisdiction and service statements are consequential choices only for users taking the applicable counter-notice route, not a general visitor requirement. Consult counsel. A general reinstatement email is not automatically a valid statutory counter-notice. Supply the original reference for requirements; the platform does not sign, swear or file on a user's behalf.

Where §512(g) applies and a valid counter-notice is received, promptly forward a copy to the original notifier and advise of intended restoration. Restore access not less than 10 and not more than 14 business days after receipt, unless the designated agent first receives the notifier's notice of an action seeking a court order restraining the related infringement. Verify timing, service and actual litigation notice; calendar days and mere silence are not the whole test. [2]

Counsel must distinguish court orders, independent lawful restrictions or an original lack of distribution permission; do not restore automatically despite separate legal grounds. Ordinary non-DMCA reinstatement requests require manual review and are not mechanically subject to this clock.

9. Repeat infringers and correction

Inform subscribers/account holders and reasonably implement termination in appropriate circumstances for repeat infringers. Consider valid notices, known facts, repetition, retractions, mistaken reports and counter-notices. Court findings are not invariably necessary; every unverified complaint is not an established violation. [1][2]

This site currently primarily accepts repository links for manual review and has no complete public-upload account or automated termination system. The owner should stop accepting submissions from traceable repeat infringers on documented grounds. Future accounts need notification, restriction/termination and correction processes. No automatic 'three strikes' system is claimed; anonymity must not defeat implementation.

10. Standard technical measures and access controls

Under §512(i), standard technical measures arise from broad consensus through an open, fair, voluntary, multi-industry process, are available on reasonable nondiscriminatory terms, and impose no substantial costs or burdens on providers. An arbitrary paid detection service is not automatically such a measure. Accommodate qualifying measures without interference. [2]

Do not bypass protected access, DRM or download controls merely because content is a skill. Anti-circumvention duties are distinct from safe-harbor questions; this policy grants no bypass permission. Restrict imports and do not execute unknown skill scripts.

11. Trademarks, patents, secrets and privacy

Section 512's copyright limits do not generally cover trademarks, patents, trade secrets, contracts, personal data or malware. Report these separately with the right type, specific material, evidence and requested action for independent legal assessment.

Avoid branding that implies endorsement or confuses source. Patent complaints should identify rights and conduct, not merely similar functionality. Limit exposure of leaked credentials, sensitive data or trade secrets without demanding publication of further secrets to substantiate a report.

12. Privacy, evidence and misrepresentation

Reports are not automatically public. Use restricted access and retain necessary records for review, communication, lawful dispute handling and preservation duties. Do not destroy required evidence. Statutory counter-notices may be copied to the original complainant, including personal contact and statements; confidentiality is not guaranteed for those disclosures.

Authorized staff or counsel assess subpoenas, orders and legally required disclosure; do not automatically publish unredacted notices. The owner must set an appropriate actual retention policy, rather than invent a universal statutory number of years.

Knowing material misrepresentation of infringement or mistaken removal can create damages and costs liability under §512(f). This does not mean every mistaken complaint is necessarily criminal. Prevent abusive complaints and permit good-faith correction. [2]

13. Owner implementation and outstanding prerequisites

Confirm the operating entity and applicable law, obtain counsel's activity-specific assessment of imports versus user-directed storage, and if appropriate complete agent registration, publication and renewal management. These facts are currently unverified; do not display DMCA certification or guaranteed safe-harbor badges.

The general email/form is not a legal case-management backend. Assign actual staff, maintain removal and no-reimport records, implement repeat-infringer handling, secure evidence, and verify APIs and static files after each removal. Automated removal, counter-notice decisions, reinstatement and account termination are not implemented by this document. Do not present written policy as already-executed operations.

Periodically review licenses, cases, agent validity, public caches and download exposure; update verified contact information and policy versions when necessary. Prevent new synchronization from redistributing materials whose permissions remain unclear.

14. Contact, version and mandatory responsibilities

General contact: Drew@skills-si.com; initial online report: /copyright#report. Include the original reference for formal notices, counter-notices and supplements. Only verified and publicly listed agent information should be called a registered agent channel.

Updated 2026-10-13. This public operational policy and owner guide is not an agency determination of eligibility and excludes no liability that law forbids excluding. It replaces neither permission, expeditious handling nor counsel. Statutory text and applicable law prevail over translation errors. Changes do not retroactively waive existing duties.

Sources and references

[1] 美国版权局：Section 512 及安全港条件 / U.S. Copyright Office: Section 512

[2] 美国法典：17 U.S.C. §512 / U.S. Code

[3] 美国版权局：指定代理登记及续期 / Designated agent FAQs

[4] GitHub：公开仓库与许可 / Licensing a repository