[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D8FAAE1R2GER4EPB29K2Q0":3,"skill-same:01M7D8FAAE1R2GER4EPB29K2Q0":112},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M7D8FAAE1R2GER4EPB29K2Q0","exploiting-insecure-data-storage-in-mobile",null,"Identifies and exploits insecure local data storage vulnerabilities in Android and iOS mobile applications including unencrypted databases, world-readable files, insecure SharedPreferences, plaintext credential storage, and improper keychain\u002Fkeystore usage. Use when performing mobile penetration testing focused on OWASP M9 (Insecure Data Storage) or assessing compliance with MASVS-STORAGE requirements. Activates for requests involving mobile data storage security, local storage exploitation, SharedPreferences analysis, or mobile data leakage assessment.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: exploiting-insecure-data-storage-in-mobile\ndescription: 'Identifies and exploits insecure local data storage vulnerabilities\n  in Android and iOS mobile applications including unencrypted databases, world-readable\n  files, insecure SharedPreferences, plaintext credential storage, and improper keychain\u002Fkeystore\n  usage. Use when performing mobile penetration testing focused on OWASP M9 (Insecure\n  Data Storage) or assessing compliance with MASVS-STORAGE requirements. Activates\n  for requests involving mobile data storage security, local storage exploitation,\n  SharedPreferences analysis, or mobile data leakage assessment.\n\n  '\ndomain: cybersecurity\nsubdomain: mobile-security\nauthor: mahipal\ntags:\n- mobile-security\n- android\n- ios\n- data-storage\n- owasp-mobile\n- penetration-testing\nversion: 1.0.0\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0057\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\n- GOVERN-1.1\n- GOVERN-4.2\nnist_csf:\n- PR.PS-01\n- PR.AA-05\n- ID.RA-01\n- DE.CM-09\nmitre_attack:\n- T1059\n- T1056\n- T1036\n- T1078\n- T1003\n---\n# Exploiting Insecure Data Storage in Mobile\n\n## When to Use\n\nUse this skill when:\n- Assessing whether mobile applications store sensitive data securely on the device filesystem\n- Testing for credential leakage through SharedPreferences, SQLite databases, or plists\n- Evaluating keychain\u002Fkeystore implementation for proper access control attributes\n- Performing data-at-rest security assessment during mobile penetration tests\n\n**Do not use** this skill on production user devices without authorization -- data extraction techniques require physical access or root\u002Fjailbreak privileges.\n\n## Prerequisites\n\n- Rooted Android device or emulator with ADB access\n- Jailbroken iOS device with SSH access or Objection-patched IPA\n- ADB (Android Debug Bridge) for Android filesystem access\n- SQLite3 CLI for database inspection\n- Frida\u002FObjection for runtime data extraction\n- Target application installed and exercised (logged in, data cached)\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1: Map Application Data Storage Locations\n\n**Android storage paths:**\n```bash\n# Internal storage (app-private, requires root)\n\u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002F\n├── shared_prefs\u002F      # SharedPreferences XML files\n├── databases\u002F         # SQLite databases\n├── files\u002F             # General files\n├── cache\u002F             # Cached data\n├── lib\u002F               # Native libraries\n└── app_webview\u002F       # WebView data\n\n# External storage (world-readable on older Android)\n\u002Fsdcard\u002FAndroid\u002Fdata\u002F\u003Cpackage_name>\u002F\n\n# Check for world-readable files\nadb shell run-as \u003Cpackage_name> ls -la \u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002F\n```\n\n**iOS storage paths:**\n```bash\n# App sandbox (accessible via SSH on jailbroken device)\n\u002Fvar\u002Fmobile\u002FContainers\u002FData\u002FApplication\u002F\u003CUUID>\u002F\n├── Documents\u002F         # User data, backed up by default\n├── Library\u002F\n│   ├── Preferences\u002F   # NSUserDefaults plists\n│   ├── Caches\u002F        # Cache data\n│   └── Application Support\u002F\n└── tmp\u002F               # Temporary files\n```\n\n### Step 2: Extract and Analyze SharedPreferences (Android)\n\n```bash\n# Pull SharedPreferences files\nadb shell run-as \u003Cpackage_name> cat shared_prefs\u002F*.xml\n\n# Or on rooted device\nadb pull \u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002Fshared_prefs\u002F .\u002Fshared_prefs\u002F\n\n# Search for sensitive data\ngrep -ri \"password\\|token\\|secret\\|key\\|session\\|auth\\|cookie\" shared_prefs\u002F\n```\n\nCommon insecure storage patterns:\n```xml\n\u003C!-- Plaintext credentials -->\n\u003Cstring name=\"user_password\">mysecretpass123\u003C\u002Fstring>\n\u003Cstring name=\"auth_token\">eyJhbGciOiJIUzI1NiIs...\u003C\u002Fstring>\n\u003Cstring name=\"api_key\">sk-live-abc123def456\u003C\u002Fstring>\n\n\u003C!-- Sensitive PII -->\n\u003Cstring name=\"user_ssn\">123-45-6789\u003C\u002Fstring>\n\u003Cstring name=\"credit_card\">4111111111111111\u003C\u002Fstring>\n```\n\n### Step 3: Analyze SQLite Databases\n\n```bash\n# Pull databases\nadb pull \u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002Fdatabases\u002F .\u002Fdatabases\u002F\n\n# Open and inspect\nsqlite3 databases\u002Fapp.db\n.tables\n.schema users\nSELECT * FROM users;\nSELECT * FROM sessions;\nSELECT * FROM tokens;\n\n# Search all tables for sensitive columns\nsqlite3 databases\u002Fapp.db \".dump\" | grep -i \"password\\|token\\|secret\\|credit\"\n```\n\nCheck for unencrypted SQLCipher databases:\n```bash\n# If database opens without password, it's unencrypted\nsqlite3 databases\u002Fapp.db \"SELECT count(*) FROM sqlite_master;\"\n# Success = unencrypted (vulnerability)\n```\n\n### Step 4: Inspect iOS Keychain Storage\n\n```bash\n# Using Objection\nobjection --gadget com.target.app explore\nios keychain dump\n\n# Check protection class attributes\n# kSecAttrAccessibleWhenUnlocked - OK for most data\n# kSecAttrAccessibleAlways - VULNERABLE: accessible even when locked\n# kSecAttrAccessibleAfterFirstUnlock - acceptable for background apps\n```\n\n### Step 5: Assess External Storage and Backup Exposure\n\n**Android:**\n```bash\n# Check if backup is enabled\naapt dump badging target.apk | grep -i \"allowBackup\"\n# android:allowBackup=\"true\" = vulnerability\n\n# Extract backup data\nadb backup -f backup.ab -apk \u003Cpackage_name>\njava -jar abe.jar unpack backup.ab backup.tar\ntar xvf backup.tar\n# Inspect extracted data for sensitive information\n\n# Check external storage\nadb shell ls -la \u002Fsdcard\u002FAndroid\u002Fdata\u002F\u003Cpackage_name>\u002F\n```\n\n**iOS:**\n```bash\n# Check backup exclusion\n# Files in Documents\u002F are backed up by default\n# Check NSURLIsExcludedFromBackupKey attribute\nobjection --gadget com.target.app explore\nios plist cat Info.plist\n```\n\n### Step 6: Runtime Memory Analysis\n\n```bash\n# Dump process memory for sensitive data\nobjection --gadget com.target.app explore\nmemory search \"password\" --string\nmemory search \"BEGIN RSA PRIVATE KEY\" --string\nmemory dump all \u002Ftmp\u002Fmemdump\u002F\n\n# Android: Check for sensitive data in logs\nadb logcat -d | grep -i \"password\\|token\\|key\\|secret\"\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **SharedPreferences** | Android key-value storage in XML format; often misused for storing credentials in plaintext |\n| **Keychain Services** | iOS secure credential storage backed by Secure Enclave hardware on modern devices |\n| **Android Keystore** | Hardware-backed cryptographic key storage on Android; keys cannot be extracted from the device |\n| **SQLCipher** | Transparent encryption extension for SQLite databases; prevents data extraction without password |\n| **Data Protection API** | iOS file-level encryption tied to device passcode; controlled via protection class attributes |\n\n## Tools & Systems\n\n- **ADB (Android Debug Bridge)**: Command-line tool for Android device interaction and filesystem access\n- **Objection**: Frida-powered runtime exploration for keychain dumping and memory inspection\n- **SQLite3**: Command-line interface for inspecting unencrypted SQLite databases\n- **Android Backup Extractor (ABE)**: Tool for unpacking ADB backup files to inspect stored data\n- **iExplorer**: GUI tool for browsing iOS app sandbox filesystem\n\n## Common Pitfalls\n\n- **Encrypted but key in code**: Some apps encrypt databases but store the encryption key in SharedPreferences or hardcoded in the binary. Always check for key storage alongside encryption.\n- **MODE_WORLD_READABLE deprecation**: This flag was deprecated in API 17, but legacy apps may still use it, making SharedPreferences readable by other apps.\n- **iOS backup scope**: By default, all files in the Documents directory are included in iTunes\u002FiCloud backups. Verify that sensitive files have the backup exclusion attribute set.\n- **Clipboard exposure**: Data copied to clipboard is accessible to all apps. Check if the app copies sensitive data (passwords, tokens) to the clipboard.\n","# Exploiting Insecure Data Storage in Mobile\n\n## When to Use\n\nUse this skill when:\n- Assessing whether mobile applications store sensitive data securely on the device filesystem\n- Testing for credential leakage through SharedPreferences, SQLite databases, or plists\n- Evaluating keychain\u002Fkeystore implementation for proper access control attributes\n- Performing data-at-rest security assessment during mobile penetration tests\n\n**Do not use** this skill on production user devices without authorization -- data extraction techniques require physical access or root\u002Fjailbreak privileges.\n\n## Prerequisites\n\n- Rooted Android device or emulator with ADB access\n- Jailbroken iOS device with SSH access or Objection-patched IPA\n- ADB (Android Debug Bridge) for Android filesystem access\n- SQLite3 CLI for database inspection\n- Frida\u002FObjection for runtime data extraction\n- Target application installed and exercised (logged in, data cached)\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1: Map Application Data Storage Locations\n\n**Android storage paths:**\n```bash\n# Internal storage (app-private, requires root)\n\u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002F\n├── shared_prefs\u002F      # SharedPreferences XML files\n├── databases\u002F         # SQLite databases\n├── files\u002F             # General files\n├── cache\u002F             # Cached data\n├── lib\u002F               # Native libraries\n└── app_webview\u002F       # WebView data\n\n# External storage (world-readable on older Android)\n\u002Fsdcard\u002FAndroid\u002Fdata\u002F\u003Cpackage_name>\u002F\n\n# Check for world-readable files\nadb shell run-as \u003Cpackage_name> ls -la \u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002F\n```\n\n**iOS storage paths:**\n```bash\n# App sandbox (accessible via SSH on jailbroken device)\n\u002Fvar\u002Fmobile\u002FContainers\u002FData\u002FApplication\u002F\u003CUUID>\u002F\n├── Documents\u002F         # User data, backed up by default\n├── Library\u002F\n│   ├── Preferences\u002F   # NSUserDefaults plists\n│   ├── Caches\u002F        # Cache data\n│   └── Application Support\u002F\n└── tmp\u002F               # Temporary files\n```\n\n### Step 2: Extract and Analyze SharedPreferences (Android)\n\n```bash\n# Pull SharedPreferences files\nadb shell run-as \u003Cpackage_name> cat shared_prefs\u002F*.xml\n\n# Or on rooted device\nadb pull \u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002Fshared_prefs\u002F .\u002Fshared_prefs\u002F\n\n# Search for sensitive data\ngrep -ri \"password\\|token\\|secret\\|key\\|session\\|auth\\|cookie\" shared_prefs\u002F\n```\n\nCommon insecure storage patterns:\n```xml\n\u003C!-- Plaintext credentials -->\n\u003Cstring name=\"user_password\">mysecretpass123\u003C\u002Fstring>\n\u003Cstring name=\"auth_token\">eyJhbGciOiJIUzI1NiIs...\u003C\u002Fstring>\n\u003Cstring name=\"api_key\">sk-live-abc123def456\u003C\u002Fstring>\n\n\u003C!-- Sensitive PII -->\n\u003Cstring name=\"user_ssn\">123-45-6789\u003C\u002Fstring>\n\u003Cstring name=\"credit_card\">4111111111111111\u003C\u002Fstring>\n```\n\n### Step 3: Analyze SQLite Databases\n\n```bash\n# Pull databases\nadb pull \u002Fdata\u002Fdata\u002F\u003Cpackage_name>\u002Fdatabases\u002F .\u002Fdatabases\u002F\n\n# Open and inspect\nsqlite3 databases\u002Fapp.db\n.tables\n.schema users\nSELECT * FROM users;\nSELECT * FROM sessions;\nSELECT * FROM tokens;\n\n# Search all tables for sensitive columns\nsqlite3 databases\u002Fapp.db \".dump\" | grep -i \"password\\|token\\|secret\\|credit\"\n```\n\nCheck for unencrypted SQLCipher databases:\n```bash\n# If database opens without password, it's unencrypted\nsqlite3 databases\u002Fapp.db \"SELECT count(*) FROM sqlite_master;\"\n# Success = unencrypted (vulnerability)\n```\n\n### Step 4: Inspect iOS Keychain Storage\n\n```bash\n# Using Objection\nobjection --gadget com.target.app explore\nios keychain dump\n\n# Check protection class attributes\n# kSecAttrAccessibleWhenUnlocked - OK for most data\n# kSecAttrAccessibleAlways - VULNERABLE: accessible even when locked\n# kSecAttrAccessibleAfterFirstUnlock - acceptable for background apps\n```\n\n### Step 5: Assess External Storage and Backup Exposure\n\n**Android:**\n```bash\n# Check if backup is enabled\naapt dump badging target.apk | grep -i \"allowBackup\"\n# android:allowBackup=\"true\" = vulnerability\n\n# Extract backup data\nadb backup -f backup.ab -apk \u003Cpackage_name>\njava -jar abe.jar unpack backup.ab backup.tar\ntar xvf backup.tar\n# Inspect extracted data for sensitive information\n\n# Check external storage\nadb shell ls -la \u002Fsdcard\u002FAndroid\u002Fdata\u002F\u003Cpackage_name>\u002F\n```\n\n**iOS:**\n```bash\n# Check backup exclusion\n# Files in Documents\u002F are backed up by default\n# Check NSURLIsExcludedFromBackupKey attribute\nobjection --gadget com.target.app explore\nios plist cat Info.plist\n```\n\n### Step 6: Runtime Memory Analysis\n\n```bash\n# Dump process memory for sensitive data\nobjection --gadget com.target.app explore\nmemory search \"password\" --string\nmemory search \"BEGIN RSA PRIVATE KEY\" --string\nmemory dump all \u002Ftmp\u002Fmemdump\u002F\n\n# Android: Check for sensitive data in logs\nadb logcat -d | grep -i \"password\\|token\\|key\\|secret\"\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **SharedPreferences** | Android key-value storage in XML format; often misused for storing credentials in plaintext |\n| **Keychain Services** | iOS secure credential storage backed by Secure Enclave hardware on modern devices |\n| **Android Keystore** | Hardware-backed cryptographic key storage on Android; keys cannot be extracted from the device |\n| **SQLCipher** | Transparent encryption extension for SQLite databases; prevents data extraction without password |\n| **Data Protection API** | iOS file-level encryption tied to device passcode; controlled via protection class attributes |\n\n## Tools & Systems\n\n- **ADB (Android Debug Bridge)**: Command-line tool for Android device interaction and filesystem access\n- **Objection**: Frida-powered runtime exploration for keychain dumping and memory inspection\n- **SQLite3**: Command-line interface for inspecting unencrypted SQLite databases\n- **Android Backup Extractor (ABE)**: Tool for unpacking ADB backup files to inspect stored data\n- **iExplorer**: GUI tool for browsing iOS app sandbox filesystem\n\n## Common Pitfalls\n\n- **Encrypted but key in code**: Some apps encrypt databases but store the encryption key in SharedPreferences or hardcoded in the binary. Always check for key storage alongside encryption.\n- **MODE_WORLD_READABLE deprecation**: This flag was deprecated in API 17, but legacy apps may still use it, making SharedPreferences readable by other apps.\n- **iOS backup scope**: By default, all files in the Documents directory are included in iTunes\u002FiCloud backups. Verify that sensitive files have the backup exclusion attribute set.\n- **Clipboard exposure**: Data copied to clipboard is accessible to all apps. Check if the app copies sensitive data (passwords, tokens) to the clipboard.\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":40,"nist_ai_rmf":41,"mitre_attack":47,"atlas_techniques":53},[26,27,28,29,30,31],"mobile-security","android","ios","data-storage","owasp-mobile","penetration-testing","mahipal","cybersecurity","1.0.0",[36,37,38,39],"PR.PS-01","PR.AA-05","ID.RA-01","DE.CM-09","Identifies and exploits insecure local data storage vulnerabilities in Android and iOS mobile applications including unencrypted databases, world-readable files, insecure SharedPreferences, plaintext credential storage, and improper keychain\u002Fkeystore usage. Use when performing mobile penetration testing focused on OWASP M9 (Insecure Data Storage) or assessing compliance with MASVS-STORAGE requirements. Activates for requests involving mobile data storage security, local storage exploitation, SharedPreferences analysis, or mobile data leakage assessment.\n",[42,43,44,45,46],"MEASURE-2.7","MAP-5.1","MANAGE-2.4","GOVERN-1.1","GOVERN-4.2",[48,49,50,51,52],"T1059","T1056","T1036","T1078","T1003",[54],"AML.T0057","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill exploiting-insecure-data-storage-in-mobile",{"tool":70,"command":71},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill exploiting-insecure-data-storage-in-mobile",{"tool":73,"command":74},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill exploiting-insecure-data-storage-in-mobile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002FSKILL.md",true,[78,84,88,94,98,102,108],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Ftemplate.md","ASSET","资产文件",1212,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002Fassets\u002Ftemplate.md",{"path":85,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fapi-reference.md","REFERENCE","参考文档",2632,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002Freferences\u002Fapi-reference.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fstandards.md",2844,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002Freferences\u002Fstandards.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fworkflows.md",3307,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002Freferences\u002Fworkflows.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fagent.py","SCRIPT","脚本",6631,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002Fscripts\u002Fagent.py",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fprocess.py",10968,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fexploiting-insecure-data-storage-in-mobile\u002Fscripts\u002Fprocess.py",[113,121,129,138,145,152],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":133,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":133,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":133,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":133,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]