Execute a phased DMARC rollout from p=none monitoring through p=quarantine to p=reject enforcement, ensuring all legitimate email sources are authenticated before blocking unauthorized senders.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionperforming-dmarc-policy-enforcement-rolloutExecute the skills CLI command in your project's root directory to begin installation:
Fetches performing-dmarc-policy-enforcement-rollout from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate performing-dmarc-policy-enforcement-rollout. Access via /performing-dmarc-policy-enforcement-rollout in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
8.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8.6K
stars
| name | performing-dmarc-policy-enforcement-rollout |
| description | Execute a phased DMARC rollout from p=none monitoring through p=quarantine to p=reject enforcement, ensuring all legitimate email sources are authenticated before blocking unauthorized senders. |
| domain | cybersecurity |
| subdomain | phishing-defense |
| tags | - dmarc - spf - dkim - email-authentication - anti-spoofing - phishing - dns - email-security |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| nist_csf | - PR.AT-01 - DE.CM-09 - RS.CO-02 - DE.AE-02 |
Domain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.
| Policy | Behavior | Use Case |
|---|---|---|
| p=none | Monitor only, no action on failures | Discovery phase |
| p=quarantine | Send failing messages to spam/junk | Transition phase |
| p=reject | Block failing messages entirely | Full enforcement |
v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; fo=1
v=DMARC1; p=none; rua=mailto:[email protected]; fo=1v=DMARC1; p=quarantine; pct=10; rua=...v=DMARC1; p=reject; pct=10; rua=...sp=reject for subdomainsPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
performing-dmarc-policy-enforcement-rollout is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
performing-dmarc-policy-enforcement-rollout fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: performing-dmarc-policy-enforcement-rollout is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for performing-dmarc-policy-enforcement-rollout matched our evaluation — installs cleanly and behaves as described in the markdown.
performing-dmarc-policy-enforcement-rollout has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: performing-dmarc-policy-enforcement-rollout is focused, and the summary matches what you get after install.
performing-dmarc-policy-enforcement-rollout has been reliable in day-to-day use. Documentation quality is above average for community skills.
performing-dmarc-policy-enforcement-rollout reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: performing-dmarc-policy-enforcement-rollout is focused, and the summary matches what you get after install.
I recommend performing-dmarc-policy-enforcement-rollout for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 30