[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPP487DVYHVCMFGXATXSFD":3,"skill-same:01M7EPP487DVYHVCMFGXATXSFD":81},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7EPP487DVYHVCMFGXATXSFD","performing-asset-criticality-scoring-for-vulns",null,"Build a multi-factor asset criticality scoring model—incorporating data sensitivity, business function dependency, regulatory scope, network exposure, and recoverability—to produce a 1-5 criticality tier that weights vulnerability prioritization and remediation SLAs. Use when prioritizing vulnerability remediation by business impact or aligning CMDB asset data with risk-based patching timelines.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-asset-criticality-scoring-for-vulns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-asset-criticality-scoring-for-vulns\ndescription: Build a multi-factor asset criticality scoring model—incorporating data\n  sensitivity, business function dependency, regulatory scope, network exposure, and\n  recoverability—to produce a 1-5 criticality tier that weights vulnerability prioritization\n  and remediation SLAs. Use when prioritizing vulnerability remediation by business\n  impact or aligning CMDB asset data with risk-based patching timelines.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- asset-criticality\n- vulnerability-prioritization\n- risk-management\n- cmdb\n- business-impact\n- crown-jewels\n- asset-classification\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\n---\n# Performing Asset Criticality Scoring for Vulns\n\n## Overview\nAsset criticality scoring assigns a business impact rating to each IT asset so that vulnerability remediation efforts focus on systems with the greatest organizational risk. Without criticality context, a CVSS 9.0 vulnerability on a test server receives the same urgency as the same vulnerability on a payment processing database. This skill covers building a multi-factor scoring model incorporating data sensitivity, business function dependency, regulatory scope, network exposure, and recoverability to create a 1-5 criticality tier that directly modifies vulnerability remediation SLAs.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing asset criticality scoring for vulns\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Configuration Management Database (CMDB) or asset inventory\n- Business Impact Analysis (BIA) data\n- Data classification policy\n- Network architecture documentation\n- Stakeholder input from business unit owners\n\n## Core Concepts\n\n### Asset Criticality Scoring Model\n\n| Factor | Weight | Score Range | Description |\n|--------|--------|-------------|-------------|\n| Business Function Impact | 25% | 1-5 | How critical is the supported business process |\n| Data Sensitivity | 25% | 1-5 | Type and sensitivity of data processed\u002Fstored |\n| Regulatory Scope | 15% | 1-5 | Regulatory requirements (PCI, HIPAA, SOX) |\n| Network Exposure | 15% | 1-5 | Internet-facing vs internal-only |\n| Recoverability | 10% | 1-5 | RTO\u002FRPO requirements, DR capability |\n| User Population | 10% | 1-5 | Number of users\u002Fcustomers affected |\n\n### Criticality Tier Definitions\n\n| Tier | Score Range | Label | SLA Modifier | Examples |\n|------|------------|-------|-------------|---------|\n| 1 | 4.5-5.0 | Crown Jewels | -50% SLA | Domain controllers, payment systems, ERP |\n| 2 | 3.5-4.4 | High Value | -25% SLA | Email servers, HR systems, CI\u002FCD |\n| 3 | 2.5-3.4 | Standard | Baseline SLA | Internal apps, file servers |\n| 4 | 1.5-2.4 | Low Impact | +25% SLA | Test environments, printers |\n| 5 | 1.0-1.4 | Minimal | +50% SLA | Decommissioning, isolated labs |\n\n### Data Sensitivity Scoring\n\n| Score | Classification | Examples |\n|-------|---------------|---------|\n| 5 | Restricted\u002FSecret | PII, PHI, payment card data, trade secrets |\n| 4 | Confidential | Financial reports, HR records, source code |\n| 3 | Internal | Internal documents, policies, project files |\n| 2 | Semi-public | Marketing materials, press releases (draft) |\n| 1 | Public | Published content, public APIs |\n\n## Workflow\n\n### Step 1: Define Scoring Criteria\n\n```python\nclass AssetCriticalityScorer:\n    \"\"\"Multi-factor asset criticality scoring engine.\"\"\"\n\n    WEIGHTS = {\n        \"business_function\": 0.25,\n        \"data_sensitivity\": 0.25,\n        \"regulatory_scope\": 0.15,\n        \"network_exposure\": 0.15,\n        \"recoverability\": 0.10,\n        \"user_population\": 0.10,\n    }\n\n    TIER_THRESHOLDS = [\n        (4.5, 1, \"Crown Jewels\", -0.50),\n        (3.5, 2, \"High Value\", -0.25),\n        (2.5, 3, \"Standard\", 0.00),\n        (1.5, 4, \"Low Impact\", 0.25),\n        (1.0, 5, \"Minimal\", 0.50),\n    ]\n\n    def score_asset(self, asset):\n        \"\"\"Calculate criticality score for an asset.\"\"\"\n        weighted_score = sum(\n            asset.get(factor, 3) * weight\n            for factor, weight in self.WEIGHTS.items()\n        )\n        score = round(weighted_score, 2)\n\n        for threshold, tier, label, sla_mod in self.TIER_THRESHOLDS:\n            if score >= threshold:\n                return {\n                    \"score\": score,\n                    \"tier\": tier,\n                    \"label\": label,\n                    \"sla_modifier\": sla_mod,\n                }\n        return {\"score\": score, \"tier\": 5, \"label\": \"Minimal\", \"sla_modifier\": 0.50}\n\n    def adjust_vuln_sla(self, base_sla_days, asset_tier_data):\n        \"\"\"Adjust vulnerability SLA based on asset criticality.\"\"\"\n        modifier = asset_tier_data[\"sla_modifier\"]\n        adjusted = int(base_sla_days * (1 + modifier))\n        return max(1, adjusted)  # Minimum 1 day SLA\n```\n\n### Step 2: Integrate with Vulnerability Prioritization\n\n```python\ndef apply_criticality_to_vulns(vulns_df, asset_scores):\n    \"\"\"Enrich vulnerability data with asset criticality context.\"\"\"\n    for idx, vuln in vulns_df.iterrows():\n        asset_id = vuln.get(\"asset_id\", \"\")\n        asset_data = asset_scores.get(asset_id, {\"tier\": 3, \"sla_modifier\": 0})\n\n        vulns_df.at[idx, \"asset_tier\"] = asset_data[\"tier\"]\n        vulns_df.at[idx, \"asset_label\"] = asset_data.get(\"label\", \"Standard\")\n\n        base_sla = get_base_sla(vuln[\"severity\"])\n        adjusted_sla = int(base_sla * (1 + asset_data[\"sla_modifier\"]))\n        vulns_df.at[idx, \"adjusted_sla_days\"] = max(1, adjusted_sla)\n\n    return vulns_df\n```\n\n## Best Practices\n1. Involve business stakeholders in criticality scoring; IT alone cannot assess business impact\n2. Review and update criticality scores at least quarterly or when systems change roles\n3. Automate scoring where possible using CMDB tags and data classification labels\n4. Apply criticality tiers to vulnerability SLAs for risk-proportional remediation\n5. Validate scoring against actual incident impact data to calibrate the model\n6. Start with a simple 3-tier model before expanding to 5 tiers\n\n## Common Pitfalls\n- Classifying all assets as \"critical\" which defeats the purpose of tiering\n- Not updating criticality scores when systems are repurposed or decommissioned\n- Using only technical factors without business context\n- Applying uniform SLAs regardless of asset importance\n- Not documenting the scoring methodology for audit and consistency\n\n## Related Skills\n- performing-cve-prioritization-with-kev-catalog\n- building-vulnerability-aging-and-sla-tracking\n- performing-business-impact-analysis\n- implementing-asset-management-program\n","# Performing Asset Criticality Scoring for Vulns\n\n## Overview\nAsset criticality scoring assigns a business impact rating to each IT asset so that vulnerability remediation efforts focus on systems with the greatest organizational risk. Without criticality context, a CVSS 9.0 vulnerability on a test server receives the same urgency as the same vulnerability on a payment processing database. This skill covers building a multi-factor scoring model incorporating data sensitivity, business function dependency, regulatory scope, network exposure, and recoverability to create a 1-5 criticality tier that directly modifies vulnerability remediation SLAs.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing asset criticality scoring for vulns\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Configuration Management Database (CMDB) or asset inventory\n- Business Impact Analysis (BIA) data\n- Data classification policy\n- Network architecture documentation\n- Stakeholder input from business unit owners\n\n## Core Concepts\n\n### Asset Criticality Scoring Model\n\n| Factor | Weight | Score Range | Description |\n|--------|--------|-------------|-------------|\n| Business Function Impact | 25% | 1-5 | How critical is the supported business process |\n| Data Sensitivity | 25% | 1-5 | Type and sensitivity of data processed\u002Fstored |\n| Regulatory Scope | 15% | 1-5 | Regulatory requirements (PCI, HIPAA, SOX) |\n| Network Exposure | 15% | 1-5 | Internet-facing vs internal-only |\n| Recoverability | 10% | 1-5 | RTO\u002FRPO requirements, DR capability |\n| User Population | 10% | 1-5 | Number of users\u002Fcustomers affected |\n\n### Criticality Tier Definitions\n\n| Tier | Score Range | Label | SLA Modifier | Examples |\n|------|------------|-------|-------------|---------|\n| 1 | 4.5-5.0 | Crown Jewels | -50% SLA | Domain controllers, payment systems, ERP |\n| 2 | 3.5-4.4 | High Value | -25% SLA | Email servers, HR systems, CI\u002FCD |\n| 3 | 2.5-3.4 | Standard | Baseline SLA | Internal apps, file servers |\n| 4 | 1.5-2.4 | Low Impact | +25% SLA | Test environments, printers |\n| 5 | 1.0-1.4 | Minimal | +50% SLA | Decommissioning, isolated labs |\n\n### Data Sensitivity Scoring\n\n| Score | Classification | Examples |\n|-------|---------------|---------|\n| 5 | Restricted\u002FSecret | PII, PHI, payment card data, trade secrets |\n| 4 | Confidential | Financial reports, HR records, source code |\n| 3 | Internal | Internal documents, policies, project files |\n| 2 | Semi-public | Marketing materials, press releases (draft) |\n| 1 | Public | Published content, public APIs |\n\n## Workflow\n\n### Step 1: Define Scoring Criteria\n\n```python\nclass AssetCriticalityScorer:\n    \"\"\"Multi-factor asset criticality scoring engine.\"\"\"\n\n    WEIGHTS = {\n        \"business_function\": 0.25,\n        \"data_sensitivity\": 0.25,\n        \"regulatory_scope\": 0.15,\n        \"network_exposure\": 0.15,\n        \"recoverability\": 0.10,\n        \"user_population\": 0.10,\n    }\n\n    TIER_THRESHOLDS = [\n        (4.5, 1, \"Crown Jewels\", -0.50),\n        (3.5, 2, \"High Value\", -0.25),\n        (2.5, 3, \"Standard\", 0.00),\n        (1.5, 4, \"Low Impact\", 0.25),\n        (1.0, 5, \"Minimal\", 0.50),\n    ]\n\n    def score_asset(self, asset):\n        \"\"\"Calculate criticality score for an asset.\"\"\"\n        weighted_score = sum(\n            asset.get(factor, 3) * weight\n            for factor, weight in self.WEIGHTS.items()\n        )\n        score = round(weighted_score, 2)\n\n        for threshold, tier, label, sla_mod in self.TIER_THRESHOLDS:\n            if score >= threshold:\n                return {\n                    \"score\": score,\n                    \"tier\": tier,\n                    \"label\": label,\n                    \"sla_modifier\": sla_mod,\n                }\n        return {\"score\": score, \"tier\": 5, \"label\": \"Minimal\", \"sla_modifier\": 0.50}\n\n    def adjust_vuln_sla(self, base_sla_days, asset_tier_data):\n        \"\"\"Adjust vulnerability SLA based on asset criticality.\"\"\"\n        modifier = asset_tier_data[\"sla_modifier\"]\n        adjusted = int(base_sla_days * (1 + modifier))\n        return max(1, adjusted)  # Minimum 1 day SLA\n```\n\n### Step 2: Integrate with Vulnerability Prioritization\n\n```python\ndef apply_criticality_to_vulns(vulns_df, asset_scores):\n    \"\"\"Enrich vulnerability data with asset criticality context.\"\"\"\n    for idx, vuln in vulns_df.iterrows():\n        asset_id = vuln.get(\"asset_id\", \"\")\n        asset_data = asset_scores.get(asset_id, {\"tier\": 3, \"sla_modifier\": 0})\n\n        vulns_df.at[idx, \"asset_tier\"] = asset_data[\"tier\"]\n        vulns_df.at[idx, \"asset_label\"] = asset_data.get(\"label\", \"Standard\")\n\n        base_sla = get_base_sla(vuln[\"severity\"])\n        adjusted_sla = int(base_sla * (1 + asset_data[\"sla_modifier\"]))\n        vulns_df.at[idx, \"adjusted_sla_days\"] = max(1, adjusted_sla)\n\n    return vulns_df\n```\n\n## Best Practices\n1. Involve business stakeholders in criticality scoring; IT alone cannot assess business impact\n2. Review and update criticality scores at least quarterly or when systems change roles\n3. Automate scoring where possible using CMDB tags and data classification labels\n4. Apply criticality tiers to vulnerability SLAs for risk-proportional remediation\n5. Validate scoring against actual incident impact data to calibrate the model\n6. Start with a simple 3-tier model before expanding to 5 tiers\n\n## Common Pitfalls\n- Classifying all assets as \"critical\" which defeats the purpose of tiering\n- Not updating criticality scores when systems are repurposed or decommissioned\n- Using only technical factors without business context\n- Applying uniform SLAs regardless of asset importance\n- Not documenting the scoring methodology for audit and consistency\n\n## Related Skills\n- performing-cve-prioritization-with-kev-catalog\n- building-vulnerability-aging-and-sla-tracking\n- performing-business-impact-analysis\n- implementing-asset-management-program\n",{"name":5,"tags":24,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41},[25,26,27,28,29,30,31],"asset-criticality","vulnerability-prioritization","risk-management","cmdb","business-impact","crown-jewels","asset-classification","mahipal","cybersecurity","1.0",[36,37,38,39],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06","vulnerability-management",[42,43,44],"T1190","T1203","T1068","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fperforming-asset-criticality-scoring-for-vulns",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-asset-criticality-scoring-for-vulns",{"tool":59,"command":60},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-asset-criticality-scoring-for-vulns",{"tool":62,"command":63},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-asset-criticality-scoring-for-vulns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-asset-criticality-scoring-for-vulns\u002FSKILL.md",true,[67,73,77],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fapi-reference.md","REFERENCE","参考文档",2244,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-asset-criticality-scoring-for-vulns\u002Freferences\u002Fapi-reference.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fstandards.md",523,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-asset-criticality-scoring-for-vulns\u002Freferences\u002Fstandards.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fworkflows.md",579,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-asset-criticality-scoring-for-vulns\u002Freferences\u002Fworkflows.md",[82,90,97,104,111,118],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]