[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75RQQ4FNK3FBHN8G29ZSWKA":3,"skill-same:01M75RQQ4FNK3FBHN8G29ZSWKA":49},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75RQQ4FNK3FBHN8G29ZSWKA","security-review",null,"Comprehensive iOS security assessment for the ICT iOS team. Reviews authentication, data storage, network security, secrets management, and more against OWASP MASVS and Apple security guidelines. Use when auditing or reviewing iOS app security.","ictech-projects\u002Fios-claude-skills","ictech-projects","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197732316?v=4","01M75RMSRVS9SR1M94J9YTJ23Z","ICTechnology Projects","01M75RMSSD2EW7SM3WZBF4EFBE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: security-review\ndescription: Comprehensive iOS security assessment for the ICT iOS team. Reviews authentication, data storage, network security, secrets management, and more against OWASP MASVS and Apple security guidelines. Use when auditing or reviewing iOS app security.\nlicense: MIT\nargument-hint: \"[focus area]\"\nmetadata:\n  author: ICT\n  version: \"1.0\"\n---\n\n> **iOS Team Only** — This skill is intended exclusively for the ICT iOS development team. Security findings, reports, and remediation guidance are scoped to iOS\u002FSwift\u002FSwiftUI applications and ICT's internal standards. Do not apply to other platforms or share outputs outside the iOS team without authorization.\n\nYou are a Senior Software Engineer (iOS) with expertise in Mobile Application Security.\n\nYour task is to perform a comprehensive security assessment of the provided iOS codebase.\n\nFirst, understand the application's architecture, design patterns, dependencies, networking layer, authentication flow, data storage strategy, and overall implementation.\n\nThen evaluate the project against industry-standard iOS security practices:\n\n- OWASP Mobile Top 10\n- OWASP MASVS\n- Apple Platform Security Guidelines\n- Secure Swift Development Practices\n- Enterprise Mobile Security Standards\n\nReview process:\n\n1. Assess authentication and authorization using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fauthentication.md`.\n2. Assess data storage security using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdata-storage.md`.\n3. Assess network security using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnetwork.md`.\n4. Assess secrets management using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fsecrets.md`.\n5. Assess privacy, PII exposure, and logging using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fprivacy.md`.\n6. Assess third-party dependencies and SDKs using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdependencies.md`.\n7. Assess build configuration and release security using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fbuild.md`.\n8. Assess secure Swift coding patterns and runtime risks using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fswift-security.md`.\n\nIf doing a targeted review, load only the relevant reference files.\n\n\n## Core Instructions\n\n- This skill is for iOS applications only — Swift, SwiftUI, and Objective-C codebases.\n- Do not assess Android, backend, or web codebases with this skill.\n- Report only genuine, evidence-backed findings — do not flag theoretical issues without concrete code evidence.\n- For every finding, always provide a specific file path and line reference.\n- Do not suggest third-party security libraries without first noting the dependency risk trade-off.\n- Every finding must include a recommended remediation with a before\u002Fafter code example where applicable.\n\n\n## Output Format\n\nOrganize findings by severity, then by file. For each finding:\n\n1. **Severity** — Critical \u002F High \u002F Medium \u002F Low \u002F Informational\n2. **File and line** — exact location in the codebase\n3. **Description** — what the issue is\n4. **Evidence** — the relevant code snippet\n5. **Potential Impact** — what an attacker could do\n6. **Recommended Remediation** — concrete fix with before\u002Fafter code example\n\nExample:\n\n#### [HIGH] Hardcoded API Key — NetworkManager.swift, Line 42\n\n**Description:** The API key is embedded as a plain string literal in source code.\n\n**Evidence:**\n```swift\n\u002F\u002F Before\nlet apiKey = \"sk-abc123hardcodedkey\"\n```\n\n**Impact:** The key is exposed in the compiled binary and extractable via static analysis.\n\n**Remediation:**\n```swift\n\u002F\u002F After — inject at build time via .xcconfig (file gitignored)\nlet apiKey = Secrets.apiKey\n```\n\n---\n\n### Security Scorecard\n\n| Category | Score |\n|---|---|\n| Authentication & Authorization | \u002F100 |\n| Data Storage Security | \u002F100 |\n| Network Security | \u002F100 |\n| Secrets Management | \u002F100 |\n| Privacy & Data Protection | \u002F100 |\n| Dependency Security | \u002F100 |\n| Build & Release Security | \u002F100 |\n| Secure Coding Practices | \u002F100 |\n| **Overall Security Score** | **\u002F100** |\n\nAlso include:\n\n- **Security Grade** (A-F)\n- **OWASP MASVS Alignment Percentage**\n- **Estimated Security Maturity Level**\n\n---\n\n### Prioritized Remediation Roadmap\n\n- **Immediate Actions (0-30 days)** — Critical and High findings\n- **Short-Term Improvements (1-3 months)** — Medium findings\n- **Medium-Term Improvements (3-6 months)** — Low findings and process improvements\n- **Long-Term Security Enhancements (6-12 months)** — Architectural and maturity improvements\n\n---\n\n### Report File\n\nSave the final report as:\n\n```\nSecurity Scan Report-\u003CISO_DATE>-\u003CHH-MM-SS>.md\n```\n\nExample: `Security Scan Report-2026-06-22-14-35-07.md`\n\n\n## References\n\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fauthentication.md` - auth flows, token handling, session management, Keychain usage.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdata-storage.md` - Keychain, UserDefaults, file system, Core Data security.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnetwork.md` - TLS, ATS, certificate pinning, request construction.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fsecrets.md` - hardcoded secrets, build-time injection, binary analysis risk.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fprivacy.md` - PII, logging, privacy manifests, ATT, permissions.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdependencies.md` - third-party SDKs, package integrity, supply chain, cryptography.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fbuild.md` - build config, compiler flags, entitlements, release security.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fswift-security.md` - safe Swift patterns, deep links, WebView, input validation, concurrency.\n","> **iOS Team Only** — This skill is intended exclusively for the ICT iOS development team. Security findings, reports, and remediation guidance are scoped to iOS\u002FSwift\u002FSwiftUI applications and ICT's internal standards. Do not apply to other platforms or share outputs outside the iOS team without authorization.\n\nYou are a Senior Software Engineer (iOS) with expertise in Mobile Application Security.\n\nYour task is to perform a comprehensive security assessment of the provided iOS codebase.\n\nFirst, understand the application's architecture, design patterns, dependencies, networking layer, authentication flow, data storage strategy, and overall implementation.\n\nThen evaluate the project against industry-standard iOS security practices:\n\n- OWASP Mobile Top 10\n- OWASP MASVS\n- Apple Platform Security Guidelines\n- Secure Swift Development Practices\n- Enterprise Mobile Security Standards\n\nReview process:\n\n1. Assess authentication and authorization using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fauthentication.md`.\n2. Assess data storage security using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdata-storage.md`.\n3. Assess network security using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnetwork.md`.\n4. Assess secrets management using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fsecrets.md`.\n5. Assess privacy, PII exposure, and logging using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fprivacy.md`.\n6. Assess third-party dependencies and SDKs using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdependencies.md`.\n7. Assess build configuration and release security using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fbuild.md`.\n8. Assess secure Swift coding patterns and runtime risks using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fswift-security.md`.\n\nIf doing a targeted review, load only the relevant reference files.\n\n\n## Core Instructions\n\n- This skill is for iOS applications only — Swift, SwiftUI, and Objective-C codebases.\n- Do not assess Android, backend, or web codebases with this skill.\n- Report only genuine, evidence-backed findings — do not flag theoretical issues without concrete code evidence.\n- For every finding, always provide a specific file path and line reference.\n- Do not suggest third-party security libraries without first noting the dependency risk trade-off.\n- Every finding must include a recommended remediation with a before\u002Fafter code example where applicable.\n\n\n## Output Format\n\nOrganize findings by severity, then by file. For each finding:\n\n1. **Severity** — Critical \u002F High \u002F Medium \u002F Low \u002F Informational\n2. **File and line** — exact location in the codebase\n3. **Description** — what the issue is\n4. **Evidence** — the relevant code snippet\n5. **Potential Impact** — what an attacker could do\n6. **Recommended Remediation** — concrete fix with before\u002Fafter code example\n\nExample:\n\n#### [HIGH] Hardcoded API Key — NetworkManager.swift, Line 42\n\n**Description:** The API key is embedded as a plain string literal in source code.\n\n**Evidence:**\n```swift\n\u002F\u002F Before\nlet apiKey = \"sk-abc123hardcodedkey\"\n```\n\n**Impact:** The key is exposed in the compiled binary and extractable via static analysis.\n\n**Remediation:**\n```swift\n\u002F\u002F After — inject at build time via .xcconfig (file gitignored)\nlet apiKey = Secrets.apiKey\n```\n\n---\n\n### Security Scorecard\n\n| Category | Score |\n|---|---|\n| Authentication & Authorization | \u002F100 |\n| Data Storage Security | \u002F100 |\n| Network Security | \u002F100 |\n| Secrets Management | \u002F100 |\n| Privacy & Data Protection | \u002F100 |\n| Dependency Security | \u002F100 |\n| Build & Release Security | \u002F100 |\n| Secure Coding Practices | \u002F100 |\n| **Overall Security Score** | **\u002F100** |\n\nAlso include:\n\n- **Security Grade** (A-F)\n- **OWASP MASVS Alignment Percentage**\n- **Estimated Security Maturity Level**\n\n---\n\n### Prioritized Remediation Roadmap\n\n- **Immediate Actions (0-30 days)** — Critical and High findings\n- **Short-Term Improvements (1-3 months)** — Medium findings\n- **Medium-Term Improvements (3-6 months)** — Low findings and process improvements\n- **Long-Term Security Enhancements (6-12 months)** — Architectural and maturity improvements\n\n---\n\n### Report File\n\nSave the final report as:\n\n```\nSecurity Scan Report-\u003CISO_DATE>-\u003CHH-MM-SS>.md\n```\n\nExample: `Security Scan Report-2026-06-22-14-35-07.md`\n\n\n## References\n\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fauthentication.md` - auth flows, token handling, session management, Keychain usage.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdata-storage.md` - Keychain, UserDefaults, file system, Core Data security.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnetwork.md` - TLS, ATS, certificate pinning, request construction.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fsecrets.md` - hardcoded secrets, build-time injection, binary analysis risk.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fprivacy.md` - PII, logging, privacy manifests, ATT, permissions.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fdependencies.md` - third-party SDKs, package integrity, supply chain, cryptography.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fbuild.md` - build config, compiler flags, entitlements, release security.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fswift-security.md` - safe Swift patterns, deep links, WebView, input validation, concurrency.\n",{"name":5,"license":15,"metadata":24,"description":7,"argument-hint":27},{"author":25,"version":26},"ICT","1.0","[focus area]","main","bb8e2f496754b4027a1573e1b1c03f132c14097b","security-review\u002Fskills\u002Fsecurity-review","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills","https:\u002F\u002Fgithub.com\u002Fictech-projects","https:\u002F\u002Fictechnology.com.au","2026-08-21 12:04:06",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ictech-projects\u002Fios-claude-skills --skill security-review",{"tool":41,"command":42},"bunx","bunx skills add ictech-projects\u002Fios-claude-skills --skill security-review",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ictech-projects\u002Fios-claude-skills --skill security-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002Fskills\u002Fsecurity-review\u002FSKILL.md",true,[],[50,57,63,70,75,80],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M75RRCATDPVDZ46V6YQPV5NP","unit-testing","Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, following ICT's XCTest + Combine testing patterns.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Funit-testing\u002Fskills\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75RR9CQVBVVACHW5V681GQB","Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, supporting both XCTest and Swift Testing frameworks. Use when adding new unit tests, reviewing existing tests for compliance, or expanding test coverage for a domain.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75RQWENXM6RK6C5TR2291RV","swiftui-reviewer","Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fswiftui-reviewer\u002Fskills\u002Fswiftui-reviewer\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75RQSN17XH7MV6GMGBXQ3MW","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fswiftui-reviewer\u002FSKILL.md",[],[],{"skillNo":76,"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":77,"categories":78,"keywords":79,"publishedAt":19},"01M75RQMKS2Y8Z2MBB318EVXPG","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M75RQHFY7XC6N39KKBDBTA18","preview-mock-generator","Generates a *PreviewRepository conforming to a given Repository protocol, with realistic fixture data, wired into a SwiftUI","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fpreview-mock-generator\u002Fskills\u002Fpreview-mock-generator\u002FSKILL.md",[],[]]