[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7WPB0EY99KBW089WVRVSA":3,"skill-same:01M6H7WPB0EY99KBW089WVRVSA":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H7WPB0EY99KBW089WVRVSA","lokalise-security-basics",null,"Apply Lokalise security best practices for API tokens and access control.\nUse when securing API tokens, implementing least privilege access,\nor auditing Lokalise security configuration.\nTrigger with phrases like \"lokalise security\", \"lokalise secrets\",\n\"secure lokalise\", \"lokalise API token security\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-security-basics\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"security","lokalise security basics","basics","Access Control","for","implementing","codex","with","trigger","io","control","tokens","code","secure","use","read","access","secrets","api","best practices","2026-11-10 10:12:30",false,"---\nname: lokalise-security-basics\ndescription: |\n  Apply Lokalise security best practices for API tokens and access control.\n  Use when securing API tokens, implementing least privilege access,\n  or auditing Lokalise security configuration.\n  Trigger with phrases like \"lokalise security\", \"lokalise secrets\",\n  \"secure lokalise\", \"lokalise API token security\".\nallowed-tools: Read, Write, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Lokalise Security Basics\n\n## Overview\nSecurity practices for Lokalise translation management integrations. Lokalise handles translation strings that may contain user-facing content, brand messaging, and occasionally PII embedded in translation keys.\n\n## Prerequisites\n- Lokalise API token provisioned\n- Understanding of token permission scopes\n- Secret management infrastructure\n\n## Instructions\n\n### Step 1: Token Scope Management\n\nLokalise tokens can have different permission levels. Use the minimum scope needed.\n\n```python\nimport os\n\n# BAD: using admin token for read-only operations\n# GOOD: create scoped tokens per use case\n\nLOKALISE_READ_TOKEN = os.environ.get(\"LOKALISE_READ_TOKEN\")    # read-only\nLOKALISE_WRITE_TOKEN = os.environ.get(\"LOKALISE_WRITE_TOKEN\")  # read + write\nLOKALISE_ADMIN_TOKEN = os.environ.get(\"LOKALISE_ADMIN_TOKEN\")  # admin (CI only)\n\ndef get_client(scope: str = \"read\"):\n    import lokalise\n    tokens = {\"read\": LOKALISE_READ_TOKEN, \"write\": LOKALISE_WRITE_TOKEN, \"admin\": LOKALISE_ADMIN_TOKEN}\n    token = tokens.get(scope)\n    if not token:\n        raise RuntimeError(f\"LOKALISE_{scope.upper()}_TOKEN not configured\")\n    return lokalise.Client(token)\n```\n\n### Step 2: Protect Translation Content\n\nTranslation strings may contain interpolation variables. Validate before processing.\n\n```python\nimport re\n\ndef validate_translation(key: str, value: str) -> list[str]:\n    issues = []\n    # Check for potential code injection in translations\n    if re.search(r'\u003Cscript|javascript:|on\\w+=', value, re.IGNORECASE):\n        issues.append(f\"Potential XSS in translation {key}\")\n    # Check for leaked credentials\n    if re.search(r'(api_key|password|secret|token)\\s*[:=]', value, re.IGNORECASE):\n        issues.append(f\"Possible credential in translation {key}\")\n    # Validate interpolation variables match expected format\n    placeholders = re.findall(r'\\{[^}]+\\}|%[sd]|\\$\\{[^}]+\\}', value)\n    for p in placeholders:\n        if re.search(r'[\u003C>\\'\"]', p):\n            issues.append(f\"Suspicious placeholder in {key}: {p}\")\n    return issues\n```\n\n### Step 3: CI\u002FCD Token Security\n\n```yaml\n# GitHub Actions: use repository secrets\nname: Sync Translations\non: push\njobs:\n  sync:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Pull translations\n        env:\n          LOKALISE_TOKEN: ${{ secrets.LOKALISE_READ_TOKEN }}\n        run: |\n          lokalise2 file download \\\n            --token $LOKALISE_TOKEN \\\n            --project-id ${{ vars.LOKALISE_PROJECT_ID }} \\\n            --format json \\\n            --dest .\u002Flocales\u002F\n```\n\n### Step 4: Audit Translation Changes\n\nTrack who changed what translations for compliance.\n\n```python\ndef audit_translation_change(project_id: str, key: str, old_value: str, new_value: str, user: str):\n    log_entry = {\n        \"timestamp\": datetime.utcnow().isoformat(),\n        \"project_id\": project_id,\n        \"key\": key,\n        \"user\": user,\n        \"action\": \"update\",\n        \"changes\": {\"old_length\": len(old_value), \"new_length\": len(new_value)}\n        # Don't log actual content if it may contain PII\n    }\n    audit_logger.info(\"Translation changed\", extra=log_entry)\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Token leaked in CI logs | Token in command output | Use environment variables, mask in CI |\n| XSS via translations | Unsanitized translation content | Validate translations before use |\n| Overprivileged access | Using admin token everywhere | Create scoped read\u002Fwrite tokens |\n| Unauthorized changes | No audit trail | Log translation changes with user info |\n\n## Examples\n\n### Security Check Script\n```bash\n# Scan for hardcoded tokens\ngrep -rn \"LOKALISE\" --include=\"*.py\" --include=\"*.ts\" src\u002F | grep -v \"os.environ\\|process.env\"\n```\n\n## Resources\n- [Lokalise API Auth](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Fapi-authentication)\n- [Lokalise Security](https:\u002F\u002Flokalise.com\u002Fsecurity)\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale","# Lokalise Security Basics\n\n## Overview\nSecurity practices for Lokalise translation management integrations. Lokalise handles translation strings that may contain user-facing content, brand messaging, and occasionally PII embedded in translation keys.\n\n## Prerequisites\n- Lokalise API token provisioned\n- Understanding of token permission scopes\n- Secret management infrastructure\n\n## Instructions\n\n### Step 1: Token Scope Management\n\nLokalise tokens can have different permission levels. Use the minimum scope needed.\n\n```python\nimport os\n\n# BAD: using admin token for read-only operations\n# GOOD: create scoped tokens per use case\n\nLOKALISE_READ_TOKEN = os.environ.get(\"LOKALISE_READ_TOKEN\")    # read-only\nLOKALISE_WRITE_TOKEN = os.environ.get(\"LOKALISE_WRITE_TOKEN\")  # read + write\nLOKALISE_ADMIN_TOKEN = os.environ.get(\"LOKALISE_ADMIN_TOKEN\")  # admin (CI only)\n\ndef get_client(scope: str = \"read\"):\n    import lokalise\n    tokens = {\"read\": LOKALISE_READ_TOKEN, \"write\": LOKALISE_WRITE_TOKEN, \"admin\": LOKALISE_ADMIN_TOKEN}\n    token = tokens.get(scope)\n    if not token:\n        raise RuntimeError(f\"LOKALISE_{scope.upper()}_TOKEN not configured\")\n    return lokalise.Client(token)\n```\n\n### Step 2: Protect Translation Content\n\nTranslation strings may contain interpolation variables. Validate before processing.\n\n```python\nimport re\n\ndef validate_translation(key: str, value: str) -> list[str]:\n    issues = []\n    # Check for potential code injection in translations\n    if re.search(r'\u003Cscript|javascript:|on\\w+=', value, re.IGNORECASE):\n        issues.append(f\"Potential XSS in translation {key}\")\n    # Check for leaked credentials\n    if re.search(r'(api_key|password|secret|token)\\s*[:=]', value, re.IGNORECASE):\n        issues.append(f\"Possible credential in translation {key}\")\n    # Validate interpolation variables match expected format\n    placeholders = re.findall(r'\\{[^}]+\\}|%[sd]|\\$\\{[^}]+\\}', value)\n    for p in placeholders:\n        if re.search(r'[\u003C>\\'\"]', p):\n            issues.append(f\"Suspicious placeholder in {key}: {p}\")\n    return issues\n```\n\n### Step 3: CI\u002FCD Token Security\n\n```yaml\n# GitHub Actions: use repository secrets\nname: Sync Translations\non: push\njobs:\n  sync:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Pull translations\n        env:\n          LOKALISE_TOKEN: ${{ secrets.LOKALISE_READ_TOKEN }}\n        run: |\n          lokalise2 file download \\\n            --token $LOKALISE_TOKEN \\\n            --project-id ${{ vars.LOKALISE_PROJECT_ID }} \\\n            --format json \\\n            --dest .\u002Flocales\u002F\n```\n\n### Step 4: Audit Translation Changes\n\nTrack who changed what translations for compliance.\n\n```python\ndef audit_translation_change(project_id: str, key: str, old_value: str, new_value: str, user: str):\n    log_entry = {\n        \"timestamp\": datetime.utcnow().isoformat(),\n        \"project_id\": project_id,\n        \"key\": key,\n        \"user\": user,\n        \"action\": \"update\",\n        \"changes\": {\"old_length\": len(old_value), \"new_length\": len(new_value)}\n        # Don't log actual content if it may contain PII\n    }\n    audit_logger.info(\"Translation changed\", extra=log_entry)\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Token leaked in CI logs | Token in command output | Use environment variables, mask in CI |\n| XSS via translations | Unsanitized translation content | Validate translations before use |\n| Overprivileged access | Using admin token everywhere | Create scoped read\u002Fwrite tokens |\n| Unauthorized changes | No audit trail | Log translation changes with user info |\n\n## Examples\n\n### Security Check Script\n```bash\n# Scan for hardcoded tokens\ngrep -rn \"LOKALISE\" --include=\"*.py\" --include=\"*.ts\" src\u002F | grep -v \"os.environ\\|process.env\"\n```\n\n## Resources\n- [Lokalise API Auth](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Fapi-authentication)\n- [Lokalise Security](https:\u002F\u002Flokalise.com\u002Fsecurity)\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Apply Lokalise security best practices for API tokens and access control.\nUse when securing API tokens, implementing least privilege access,\nor auditing Lokalise security configuration.\nTrigger with phrases like \"lokalise security\", \"lokalise secrets\",\n\"secure lokalise\", \"lokalise API token security\".\n","Read, Write, Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-security-basics",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill lokalise-security-basics",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill lokalise-security-basics",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill lokalise-security-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-security-basics\u002FSKILL.md",true,[],[70,105,133,150,170,195],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":86,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[76,81],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,36,96,97,98,99,100,101,102,103,104,22],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":119,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[111,112,115,118],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":113,"categoryName":114,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":116,"categoryName":117,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[120,121,122,123,88,124,30,125,126,127,128,129,36,96,102,130,131,103,132,23],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[139],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[141,142,143,18,88,91,36,96,34,32,144,145,21,146,147,103,148,149,23,22],"policy","authoring","apim policy authoring","ready","api security","error","processing","cors configuration","production-ready",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":158,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[156,157],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[159,18,160,36,145,161,88,120,162,163,164,165,96,166,103,167,168,169,104,22],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[177,178,179,122,180,181,182,183,36,184,185,186,187,188,189,190,191,192,193,194],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[197,202,203,204,205,206,207,32,208,209],"npm","js","calculate","node","math","user","compute","errors"]