[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-splunk-field-extraction-and-cim-mapping":3,"mdc-ls53xp-key":34,"related-repo-splunk-field-extraction-and-cim-mapping":480,"related-org-splunk-field-extraction-and-cim-mapping":583},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"field-extraction-and-cim-mapping","map and extract Splunk fields","Author, explain, diagnose, and validate Splunk search-time field extractions and mappings to Common Information Model (CIM) datasets from representative events, configuration, and search evidence. Use for automatic key-value extraction, regex or delimiter extraction, props.conf EXTRACT and REPORT\u002Ftransforms.conf rules, SPL extraction commands, aliases, calculated fields, lookups, event types, tags, value normalization, CIM field mapping, and missing or incorrect normalization; do not use for deployment execution, ingestion transport, app installation, knowledge-object governance, data-model acceleration, or unrelated search\u002Fdashboard repair.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"splunk","Splunk","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fsplunk.jpg",[12,16,19,20],{"name":13,"slug":14,"type":15},"Data Quality","data-quality","tag",{"name":17,"slug":18,"type":15},"Data Extraction","data-extraction",{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},"Search","search",3,"https:\u002F\u002Fgithub.com\u002Fsplunk\u002Fsplunk-agent-skills","2026-08-15T03:47:41.482605","Apache-2.0",0,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Open source, enterprise-ready AI skills for Splunk use cases, built for secure discovery, consistent execution, and production-grade customer workflows.","https:\u002F\u002Fgithub.com\u002Fsplunk\u002Fsplunk-agent-skills\u002Ftree\u002FHEAD\u002Fskills\u002Ffield-extraction-and-cim-mapping","---\nname: field-extraction-and-cim-mapping\ndescription: Author, explain, diagnose, and validate Splunk search-time field extractions and mappings to Common Information Model (CIM) datasets from representative events, configuration, and search evidence. Use for automatic key-value extraction, regex or delimiter extraction, props.conf EXTRACT and REPORT\u002Ftransforms.conf rules, SPL extraction commands, aliases, calculated fields, lookups, event types, tags, value normalization, CIM field mapping, and missing or incorrect normalization; do not use for deployment execution, ingestion transport, app installation, knowledge-object governance, data-model acceleration, or unrelated search\u002Fdashboard repair.\nlicense: Apache-2.0\nallowed-tools:\n  - web\nmetadata:\n  splunk:\n    domain: data-normalization\n    products:\n      - splunk-cloud-platform\n      - splunk-enterprise\n    entities:\n      - search-time field extractions\n      - props.conf and transforms.conf\n      - field aliases, calculated fields, and lookups\n      - event types and tags\n      - CIM datasets and normalized fields\n    triggers:\n      - extract fields from sample events\n      - write EXTRACT or REPORT rules\n      - map fields to CIM\n      - validate CIM normalization\n      - diagnose missing fields, aliases, lookups, tags, or event types\n    not-for:\n      - data-model acceleration or tstats tuning\n      - HEC, transport, index routing, or source onboarding\n      - app installation, Cloud changes, or cluster deployment\n      - knowledge-object governance or lifecycle review\n      - unrelated SPL, search, or dashboard troubleshooting\n    outcomes:\n      - cited extraction-mechanism guidance\n      - evidence-bound extraction draft\n      - semantic CIM mapping plan\n      - unverified validation workflow or evidence-based result\n      - bounded normalization-gap diagnosis\n---\n\n# Field Extraction and CIM Mapping\n\nProduce documentation-backed, evidence-bound guidance for search-time field\nextraction and CIM normalization. Draft text artifacts only. Never authenticate\nto, modify, install on, or deploy to a Splunk environment.\n\n## Prerequisites\n\nRecord or ask for only the missing items material to the requested decision:\n\n- representative sanitized raw events, including meaningful edge cases;\n- sourcetype and relevant current `props.conf`, `transforms.conf`, SPL, aliases,\n  calculated fields, lookups, event types, and tags;\n- desired source fields and their meanings;\n- target CIM dataset and installed CIM version or model details;\n- Splunk product\u002Fversion, persistence scope, app context, and deployment\n  topology when configuration or routing depends on them; and\n- observed field\u002Fsearch\u002Fdata-model validation output when diagnosing or\n  claiming validation.\n\nNever invent event structure or field meaning. With partial evidence, first\npreserve and assess every supported object-level fact. Mark each absent field\nor artifact `unknown`, and gate only the conclusion it affects; missing context\nmust not erase supplied evidence. Clearly separate supplied observations,\ndocumented facts, assumptions, provisional conclusions, and unverified steps.\n\n## When to Use\n\nUse this skill when the primary outcome is documented extraction guidance, an\nevidence-bound extraction draft, a semantic CIM mapping, validation steps, or a\nnormalization-gap diagnosis. Apply the boundaries below to adjacent work.\n\n## Workflow Overview\n\n### 1. Select the extraction mechanism\n\nRead [public-guidance.md](references\u002Fpublic-guidance.md). Identify the documented\nmechanism that fits the event shape: automatic key-value extraction, regex or\ndelimiter extraction, inline `EXTRACT`, reusable `REPORT` plus\n`transforms.conf`, or an ad hoc SPL command. Separate persistent knowledge\nobjects from search-local SPL. Treat index-time extraction as a\nperformance-sensitive exception, not the default.\n\nIf source events or deployment context are absent, give only cited general\nguidance. End the answer with a direct request for representative events,\nsourcetype, product and version, and desired persistence scope before proposing\nconcrete configuration; merely listing these inputs as absent does not satisfy\nthe request.\n\n### 2. Draft an evidence-bound extraction\n\nUse the smallest approach that targets the supplied samples. Provide concrete\n`props.conf`, `transforms.conf`, or SPL only when representative events and\ndesired fields are supplied. Explain why it matches the event shape and state\nassumptions about sourcetype, app context, delimiters, cardinality, multivalue\nbehavior, and persistent search-time versus ad hoc scope.\n\nFlag broad unnecessary key-value extraction, unbounded variable-key expansion,\nduplicated calculated-field logic, brittle sample-only matching, and premature\nindex-time extraction. If evidence is insufficient, ask for the missing sample\nand desired fields or give only a clearly marked, unvalidated template\u002Fchecklist.\n\n### 3. Build a semantic CIM mapping plan\n\nName the target CIM dataset; if event meaning permits several candidates, ask\nthe user to choose and explain the candidates provisionally. Map by source-field\nsemantics, not name similarity. Where evidence permits, distinguish required\nfields, recommended or expected fields, required tags, dataset constraints,\naliases, calculated fields, lookups, event types, enrichment, and value\nnormalization.\n\nIf the target dataset, source semantics, or installed model details are\nmissing, preserve any supported field facts, label candidate mappings\nprovisional, and request the smallest missing evidence. Direct the user to the\nData Model Editor or installed model JSON for complete constraints and inherited\nfields; do not claim the public reference tables are complete.\n\n### 4. Define or assess validation\n\nProvide the relevant inspection path: normal search field inspection,\nPivot\u002FDatasets, `datamodel` or `from datamodel`, `datamodelsimple`, or the CIM\nValidation data model's Missing Extractions and Untagged Events datasets. State\nthe expected success evidence: correct values appear, required tags\u002Fevent types\nselect the intended events, and edge cases preserve extraction behavior.\n\nCall runtime validation `unverified` unless actual search or deployment results\nare supplied. When results are absent, provide only commands and expected\nobservations. When results are present, assess only what they demonstrate.\n\nKeep a validation-only answer bounded. Use one short status statement, at most\nfive focused validation steps, and one compact expected-evidence checklist.\nPrefer one representative search per distinct validation purpose instead of\nenumerating variants. Do not repeat prerequisites, boundaries, citations, or\nthe same caveat in multiple sections. A validation-only answer must be 900\nwords or fewer. If the user requests a longer runbook, first return a complete\nvalidation answer within this limit; provide the longer runbook only afterward.\n\n### 5. Diagnose normalization gaps\n\nConnect every suspected missing or incorrect extraction, alias, lookup, tag,\nevent type, calculated field, or CIM mapping to a supplied raw event,\nconfiguration fragment, field output, or data-model validation result. Preserve\nconfirmed facts even when other artifacts are absent.\n\nSeparate semantic\u002Fconfiguration explanations from possible deployment,\napp-installation, cluster-bundle, managed Cloud change, or acceleration causes.\nProvide a bounded semantic remediation plan and the exact evidence needed to\nconfirm it. If only symptoms are supplied, do not diagnose: ask for the smallest\nsafe subset of representative events, relevant current configuration, search\noutput, target dataset, product\u002Fversion, and topology needed for the pending\ndecision.\n\n## Boundaries\n\nKeep extraction authoring and CIM-mapping semantics here. Route only work that\ncrosses the boundary:\n\n- governance, ownership, naming, packaging policy, and lifecycle decisions to\n  Knowledge Object Governance;\n- source onboarding transport, HEC, tokens, and index routing to the relevant\n  ingestion owner;\n- acceleration design, `tstats` tuning, summaries, and acceleration failures to\n  Data Model and Search Acceleration;\n- unrelated search\u002Fdashboard remediation to its troubleshooting owner; and\n- app installation, managed Cloud changes, cluster bundles, approvals, and\n  production deployment to the appropriate Splunk operator.\n\nDo not claim runtime verification, publication readiness, prevalence,\ncross-system linkage, telemetry baselines, or rollback readiness without direct\nevidence.\n\n## Examples\n\n- “Choose a persistent extraction for these sanitized events and fields.”\n- “Map these existing fields to the Authentication CIM dataset.”\n- “Assess these Missing Extractions results against the supplied config.”\n\n## Troubleshooting\n\n- No samples: provide cited mechanism guidance or an unvalidated template, then\n  request representative events and desired fields.\n- Partial artifacts: retain every supported fact, mark only missing facts\n  unknown, and gate only the affected mapping or diagnosis.\n- No runtime results: provide validation commands and expected observations;\n  label validation unverified.\n- Operational cause remains possible: separate it from the semantic finding and\n  route only the operational action that crosses the boundary.\n\n## Final-answer contract\n\nBefore returning, verify:\n\n- Put a point-of-use public citation beside every decisive\n  documentation-backed action or claim.\n- Before evidence-dependent diagnosis, request the smallest safe evidence set;\n  preserve every supported object-level fact and let absent fields limit only\n  the affected conclusion.\n- State assumptions, expected success evidence, and what remains provisional or\n  unverified.\n- Name an owner or route only when the answer crosses this skill's boundary;\n  otherwise state that the answer remains within bounded field-extraction and\n  CIM-mapping scope.\n",{"data":35,"body":68},{"name":4,"description":6,"license":26,"allowed-tools":36,"metadata":38},[37],"web",{"splunk":39},{"domain":40,"products":41,"entities":44,"triggers":50,"not-for":56,"outcomes":62},"data-normalization",[42,43],"splunk-cloud-platform","splunk-enterprise",[45,46,47,48,49],"search-time field extractions","props.conf and transforms.conf","field aliases, calculated fields, and lookups","event types and tags","CIM datasets and normalized fields",[51,52,53,54,55],"extract fields from sample events","write EXTRACT or REPORT rules","map fields to CIM","validate CIM normalization","diagnose missing fields, aliases, lookups, tags, or event types",[57,58,59,60,61],"data-model acceleration or tstats tuning","HEC, transport, index routing, or source onboarding","app installation, Cloud changes, or cluster deployment","knowledge-object governance or lifecycle review","unrelated SPL, search, or dashboard troubleshooting",[63,64,65,66,67],"cited extraction-mechanism guidance","evidence-bound extraction draft","semantic CIM mapping plan","unverified validation workflow or evidence-based result","bounded normalization-gap diagnosis",{"type":69,"children":70},"root",[71,79,85,92,97,149,162,168,173,179,186,223,228,234,252,257,263,268,273,279,307,320,325,331,336,341,347,352,388,393,399,417,423,446,452,457],{"type":72,"tag":73,"props":74,"children":75},"element","h1",{"id":4},[76],{"type":77,"value":78},"text","Field Extraction and CIM Mapping",{"type":72,"tag":80,"props":81,"children":82},"p",{},[83],{"type":77,"value":84},"Produce documentation-backed, evidence-bound guidance for search-time field\nextraction and CIM normalization. Draft text artifacts only. Never authenticate\nto, modify, install on, or deploy to a Splunk environment.",{"type":72,"tag":86,"props":87,"children":89},"h2",{"id":88},"prerequisites",[90],{"type":77,"value":91},"Prerequisites",{"type":72,"tag":80,"props":93,"children":94},{},[95],{"type":77,"value":96},"Record or ask for only the missing items material to the requested decision:",{"type":72,"tag":98,"props":99,"children":100},"ul",{},[101,107,129,134,139,144],{"type":72,"tag":102,"props":103,"children":104},"li",{},[105],{"type":77,"value":106},"representative sanitized raw events, including meaningful edge cases;",{"type":72,"tag":102,"props":108,"children":109},{},[110,112,119,121,127],{"type":77,"value":111},"sourcetype and relevant current ",{"type":72,"tag":113,"props":114,"children":116},"code",{"className":115},[],[117],{"type":77,"value":118},"props.conf",{"type":77,"value":120},", ",{"type":72,"tag":113,"props":122,"children":124},{"className":123},[],[125],{"type":77,"value":126},"transforms.conf",{"type":77,"value":128},", SPL, aliases,\ncalculated fields, lookups, event types, and tags;",{"type":72,"tag":102,"props":130,"children":131},{},[132],{"type":77,"value":133},"desired source fields and their meanings;",{"type":72,"tag":102,"props":135,"children":136},{},[137],{"type":77,"value":138},"target CIM dataset and installed CIM version or model details;",{"type":72,"tag":102,"props":140,"children":141},{},[142],{"type":77,"value":143},"Splunk product\u002Fversion, persistence scope, app context, and deployment\ntopology when configuration or routing depends on them; and",{"type":72,"tag":102,"props":145,"children":146},{},[147],{"type":77,"value":148},"observed field\u002Fsearch\u002Fdata-model validation output when diagnosing or\nclaiming validation.",{"type":72,"tag":80,"props":150,"children":151},{},[152,154,160],{"type":77,"value":153},"Never invent event structure or field meaning. With partial evidence, first\npreserve and assess every supported object-level fact. Mark each absent field\nor artifact ",{"type":72,"tag":113,"props":155,"children":157},{"className":156},[],[158],{"type":77,"value":159},"unknown",{"type":77,"value":161},", and gate only the conclusion it affects; missing context\nmust not erase supplied evidence. Clearly separate supplied observations,\ndocumented facts, assumptions, provisional conclusions, and unverified steps.",{"type":72,"tag":86,"props":163,"children":165},{"id":164},"when-to-use",[166],{"type":77,"value":167},"When to Use",{"type":72,"tag":80,"props":169,"children":170},{},[171],{"type":77,"value":172},"Use this skill when the primary outcome is documented extraction guidance, an\nevidence-bound extraction draft, a semantic CIM mapping, validation steps, or a\nnormalization-gap diagnosis. Apply the boundaries below to adjacent work.",{"type":72,"tag":86,"props":174,"children":176},{"id":175},"workflow-overview",[177],{"type":77,"value":178},"Workflow Overview",{"type":72,"tag":180,"props":181,"children":183},"h3",{"id":182},"_1-select-the-extraction-mechanism",[184],{"type":77,"value":185},"1. Select the extraction mechanism",{"type":72,"tag":80,"props":187,"children":188},{},[189,191,198,200,206,208,214,216,221],{"type":77,"value":190},"Read ",{"type":72,"tag":192,"props":193,"children":195},"a",{"href":194},"references\u002Fpublic-guidance.md",[196],{"type":77,"value":197},"public-guidance.md",{"type":77,"value":199},". Identify the documented\nmechanism that fits the event shape: automatic key-value extraction, regex or\ndelimiter extraction, inline ",{"type":72,"tag":113,"props":201,"children":203},{"className":202},[],[204],{"type":77,"value":205},"EXTRACT",{"type":77,"value":207},", reusable ",{"type":72,"tag":113,"props":209,"children":211},{"className":210},[],[212],{"type":77,"value":213},"REPORT",{"type":77,"value":215}," plus\n",{"type":72,"tag":113,"props":217,"children":219},{"className":218},[],[220],{"type":77,"value":126},{"type":77,"value":222},", or an ad hoc SPL command. Separate persistent knowledge\nobjects from search-local SPL. Treat index-time extraction as a\nperformance-sensitive exception, not the default.",{"type":72,"tag":80,"props":224,"children":225},{},[226],{"type":77,"value":227},"If source events or deployment context are absent, give only cited general\nguidance. End the answer with a direct request for representative events,\nsourcetype, product and version, and desired persistence scope before proposing\nconcrete configuration; merely listing these inputs as absent does not satisfy\nthe request.",{"type":72,"tag":180,"props":229,"children":231},{"id":230},"_2-draft-an-evidence-bound-extraction",[232],{"type":77,"value":233},"2. Draft an evidence-bound extraction",{"type":72,"tag":80,"props":235,"children":236},{},[237,239,244,245,250],{"type":77,"value":238},"Use the smallest approach that targets the supplied samples. Provide concrete\n",{"type":72,"tag":113,"props":240,"children":242},{"className":241},[],[243],{"type":77,"value":118},{"type":77,"value":120},{"type":72,"tag":113,"props":246,"children":248},{"className":247},[],[249],{"type":77,"value":126},{"type":77,"value":251},", or SPL only when representative events and\ndesired fields are supplied. Explain why it matches the event shape and state\nassumptions about sourcetype, app context, delimiters, cardinality, multivalue\nbehavior, and persistent search-time versus ad hoc scope.",{"type":72,"tag":80,"props":253,"children":254},{},[255],{"type":77,"value":256},"Flag broad unnecessary key-value extraction, unbounded variable-key expansion,\nduplicated calculated-field logic, brittle sample-only matching, and premature\nindex-time extraction. If evidence is insufficient, ask for the missing sample\nand desired fields or give only a clearly marked, unvalidated template\u002Fchecklist.",{"type":72,"tag":180,"props":258,"children":260},{"id":259},"_3-build-a-semantic-cim-mapping-plan",[261],{"type":77,"value":262},"3. Build a semantic CIM mapping plan",{"type":72,"tag":80,"props":264,"children":265},{},[266],{"type":77,"value":267},"Name the target CIM dataset; if event meaning permits several candidates, ask\nthe user to choose and explain the candidates provisionally. Map by source-field\nsemantics, not name similarity. Where evidence permits, distinguish required\nfields, recommended or expected fields, required tags, dataset constraints,\naliases, calculated fields, lookups, event types, enrichment, and value\nnormalization.",{"type":72,"tag":80,"props":269,"children":270},{},[271],{"type":77,"value":272},"If the target dataset, source semantics, or installed model details are\nmissing, preserve any supported field facts, label candidate mappings\nprovisional, and request the smallest missing evidence. Direct the user to the\nData Model Editor or installed model JSON for complete constraints and inherited\nfields; do not claim the public reference tables are complete.",{"type":72,"tag":180,"props":274,"children":276},{"id":275},"_4-define-or-assess-validation",[277],{"type":77,"value":278},"4. Define or assess validation",{"type":72,"tag":80,"props":280,"children":281},{},[282,284,290,292,298,299,305],{"type":77,"value":283},"Provide the relevant inspection path: normal search field inspection,\nPivot\u002FDatasets, ",{"type":72,"tag":113,"props":285,"children":287},{"className":286},[],[288],{"type":77,"value":289},"datamodel",{"type":77,"value":291}," or ",{"type":72,"tag":113,"props":293,"children":295},{"className":294},[],[296],{"type":77,"value":297},"from datamodel",{"type":77,"value":120},{"type":72,"tag":113,"props":300,"children":302},{"className":301},[],[303],{"type":77,"value":304},"datamodelsimple",{"type":77,"value":306},", or the CIM\nValidation data model's Missing Extractions and Untagged Events datasets. State\nthe expected success evidence: correct values appear, required tags\u002Fevent types\nselect the intended events, and edge cases preserve extraction behavior.",{"type":72,"tag":80,"props":308,"children":309},{},[310,312,318],{"type":77,"value":311},"Call runtime validation ",{"type":72,"tag":113,"props":313,"children":315},{"className":314},[],[316],{"type":77,"value":317},"unverified",{"type":77,"value":319}," unless actual search or deployment results\nare supplied. When results are absent, provide only commands and expected\nobservations. When results are present, assess only what they demonstrate.",{"type":72,"tag":80,"props":321,"children":322},{},[323],{"type":77,"value":324},"Keep a validation-only answer bounded. Use one short status statement, at most\nfive focused validation steps, and one compact expected-evidence checklist.\nPrefer one representative search per distinct validation purpose instead of\nenumerating variants. Do not repeat prerequisites, boundaries, citations, or\nthe same caveat in multiple sections. A validation-only answer must be 900\nwords or fewer. If the user requests a longer runbook, first return a complete\nvalidation answer within this limit; provide the longer runbook only afterward.",{"type":72,"tag":180,"props":326,"children":328},{"id":327},"_5-diagnose-normalization-gaps",[329],{"type":77,"value":330},"5. Diagnose normalization gaps",{"type":72,"tag":80,"props":332,"children":333},{},[334],{"type":77,"value":335},"Connect every suspected missing or incorrect extraction, alias, lookup, tag,\nevent type, calculated field, or CIM mapping to a supplied raw event,\nconfiguration fragment, field output, or data-model validation result. Preserve\nconfirmed facts even when other artifacts are absent.",{"type":72,"tag":80,"props":337,"children":338},{},[339],{"type":77,"value":340},"Separate semantic\u002Fconfiguration explanations from possible deployment,\napp-installation, cluster-bundle, managed Cloud change, or acceleration causes.\nProvide a bounded semantic remediation plan and the exact evidence needed to\nconfirm it. If only symptoms are supplied, do not diagnose: ask for the smallest\nsafe subset of representative events, relevant current configuration, search\noutput, target dataset, product\u002Fversion, and topology needed for the pending\ndecision.",{"type":72,"tag":86,"props":342,"children":344},{"id":343},"boundaries",[345],{"type":77,"value":346},"Boundaries",{"type":72,"tag":80,"props":348,"children":349},{},[350],{"type":77,"value":351},"Keep extraction authoring and CIM-mapping semantics here. Route only work that\ncrosses the boundary:",{"type":72,"tag":98,"props":353,"children":354},{},[355,360,365,378,383],{"type":72,"tag":102,"props":356,"children":357},{},[358],{"type":77,"value":359},"governance, ownership, naming, packaging policy, and lifecycle decisions to\nKnowledge Object Governance;",{"type":72,"tag":102,"props":361,"children":362},{},[363],{"type":77,"value":364},"source onboarding transport, HEC, tokens, and index routing to the relevant\ningestion owner;",{"type":72,"tag":102,"props":366,"children":367},{},[368,370,376],{"type":77,"value":369},"acceleration design, ",{"type":72,"tag":113,"props":371,"children":373},{"className":372},[],[374],{"type":77,"value":375},"tstats",{"type":77,"value":377}," tuning, summaries, and acceleration failures to\nData Model and Search Acceleration;",{"type":72,"tag":102,"props":379,"children":380},{},[381],{"type":77,"value":382},"unrelated search\u002Fdashboard remediation to its troubleshooting owner; and",{"type":72,"tag":102,"props":384,"children":385},{},[386],{"type":77,"value":387},"app installation, managed Cloud changes, cluster bundles, approvals, and\nproduction deployment to the appropriate Splunk operator.",{"type":72,"tag":80,"props":389,"children":390},{},[391],{"type":77,"value":392},"Do not claim runtime verification, publication readiness, prevalence,\ncross-system linkage, telemetry baselines, or rollback readiness without direct\nevidence.",{"type":72,"tag":86,"props":394,"children":396},{"id":395},"examples",[397],{"type":77,"value":398},"Examples",{"type":72,"tag":98,"props":400,"children":401},{},[402,407,412],{"type":72,"tag":102,"props":403,"children":404},{},[405],{"type":77,"value":406},"“Choose a persistent extraction for these sanitized events and fields.”",{"type":72,"tag":102,"props":408,"children":409},{},[410],{"type":77,"value":411},"“Map these existing fields to the Authentication CIM dataset.”",{"type":72,"tag":102,"props":413,"children":414},{},[415],{"type":77,"value":416},"“Assess these Missing Extractions results against the supplied config.”",{"type":72,"tag":86,"props":418,"children":420},{"id":419},"troubleshooting",[421],{"type":77,"value":422},"Troubleshooting",{"type":72,"tag":98,"props":424,"children":425},{},[426,431,436,441],{"type":72,"tag":102,"props":427,"children":428},{},[429],{"type":77,"value":430},"No samples: provide cited mechanism guidance or an unvalidated template, then\nrequest representative events and desired fields.",{"type":72,"tag":102,"props":432,"children":433},{},[434],{"type":77,"value":435},"Partial artifacts: retain every supported fact, mark only missing facts\nunknown, and gate only the affected mapping or diagnosis.",{"type":72,"tag":102,"props":437,"children":438},{},[439],{"type":77,"value":440},"No runtime results: provide validation commands and expected observations;\nlabel validation unverified.",{"type":72,"tag":102,"props":442,"children":443},{},[444],{"type":77,"value":445},"Operational cause remains possible: separate it from the semantic finding and\nroute only the operational action that crosses the boundary.",{"type":72,"tag":86,"props":447,"children":449},{"id":448},"final-answer-contract",[450],{"type":77,"value":451},"Final-answer contract",{"type":72,"tag":80,"props":453,"children":454},{},[455],{"type":77,"value":456},"Before returning, verify:",{"type":72,"tag":98,"props":458,"children":459},{},[460,465,470,475],{"type":72,"tag":102,"props":461,"children":462},{},[463],{"type":77,"value":464},"Put a point-of-use public citation beside every decisive\ndocumentation-backed action or claim.",{"type":72,"tag":102,"props":466,"children":467},{},[468],{"type":77,"value":469},"Before evidence-dependent diagnosis, request the smallest safe evidence set;\npreserve every supported object-level fact and let absent fields limit only\nthe affected conclusion.",{"type":72,"tag":102,"props":471,"children":472},{},[473],{"type":77,"value":474},"State assumptions, expected success evidence, and what remains provisional or\nunverified.",{"type":72,"tag":102,"props":476,"children":477},{},[478],{"type":77,"value":479},"Name an owner or route only when the answer crosses this skill's boundary;\notherwise state that the answer remains within bounded field-extraction and\nCIM-mapping scope.",{"items":481,"total":582},[482,499,515,528,535,550,567],{"slug":483,"name":483,"fn":484,"description":485,"org":486,"tags":487,"stars":23,"repoUrl":24,"updatedAt":498},"app-and-add-on-lifecycle-advisor","manage Splunk app and add-on lifecycle","Give cited, advisory-only Splunk app and add-on lifecycle guidance and assess supplied compatibility, installation, upgrade, validation, deprecation, migration, and removal evidence. Use when a Splunk Cloud Platform or Splunk Enterprise administrator needs packaging or AppInspect guidance, environment-specific readiness classification, a non-mutating lifecycle plan, or safe-removal review for a named app\u002Fadd-on and Splunk version. Route fact-only metadata lookup, platform upgrade execution, fleet rollout, vulnerability remediation, and knowledge-object governance beyond removal-impact checks to their owning workflows.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[488,491,494,497],{"name":489,"slug":490,"type":15},"Deployment","deployment",{"name":492,"slug":493,"type":15},"Maintenance","maintenance",{"name":495,"slug":496,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-08-15T03:47:43.931312",{"slug":500,"name":500,"fn":501,"description":502,"org":503,"tags":504,"stars":23,"repoUrl":24,"updatedAt":514},"custom-visualization-builder","build and install custom Splunk visualizations","Scaffold, build, package, and install a custom visualization into Splunk using the dashboard-studio-extension framework. Use when the user wants to create a new custom viz, add a visualization to an existing project, or migrate a legacy custom viz.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[505,508,511],{"name":506,"slug":507,"type":15},"Plugin Development","plugin-development",{"name":509,"slug":510,"type":15},"UI Components","ui-components",{"name":512,"slug":513,"type":15},"Visualization","visualization","2026-08-02T06:09:08.393955",{"slug":516,"name":516,"fn":517,"description":518,"org":519,"tags":520,"stars":23,"repoUrl":24,"updatedAt":527},"deployment-server-and-forwarder-fleet-management","manage Splunk forwarder fleet","Explain, plan, and diagnose Splunk Enterprise Deployment Server and 10.x Agent Management fleet behavior from public documentation and sanitized evidence. Use for terminology, deployment apps, server classes, client filters, phone-home, effective assignment, rollout verification, cache or reload behavior, scale tuning, fleet visibility, and Deployment Server delivery of Splunk Remote Upgrader content; do not use for unrelated forwarder data flow, HEC, cluster bundle\u002Fdeployer work, or live mutations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[521,522,525,526],{"name":489,"slug":490,"type":15},{"name":523,"slug":524,"type":15},"Infrastructure","infrastructure",{"name":495,"slug":496,"type":15},{"name":9,"slug":8,"type":15},"2026-08-15T03:47:44.281337",{"slug":4,"name":4,"fn":5,"description":6,"org":529,"tags":530,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[531,532,533,534],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":21,"slug":22,"type":15},{"name":9,"slug":8,"type":15},{"slug":536,"name":536,"fn":537,"description":538,"org":539,"tags":540,"stars":23,"repoUrl":24,"updatedAt":549},"hec-setup-and-troubleshooting","configure and troubleshoot Splunk HEC","Set up and validate Splunk HTTP Event Collector (HEC), explain indexer acknowledgment and distributed HEC behavior, diagnose HEC no-data and HTTP delivery failures from sanitized evidence, and prepare bounded escalation handoffs. Use for Splunk Cloud Platform or Splunk Enterprise HEC tokens, endpoints, event or raw payloads, TLS, channels, ACK, health, authorization, queues, and delivery verification; do not use for non-HEC ingestion, broad architecture, allowlist changes, or service-side remediation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[541,544,547,548],{"name":542,"slug":543,"type":15},"Debugging","debugging",{"name":545,"slug":546,"type":15},"HTTP","http",{"name":495,"slug":496,"type":15},{"name":9,"slug":8,"type":15},"2026-08-11T04:26:30.091865",{"slug":551,"name":551,"fn":552,"description":553,"org":554,"tags":555,"stars":23,"repoUrl":24,"updatedAt":566},"knowledge-object-governance","govern Splunk knowledge objects","Give cited public Splunk knowledge-object governance guidance and assess user-authorized inventory, ownership, orphan, ACL, naming, lifecycle, lookup, and search-head-cluster comparison evidence without changing a deployment. Use for shared lookups, sourcetypes, saved searches, macros, field extractions, aliases, props\u002Ftransforms, CIM mappings, dashboards, reports, and related objects when an administrator needs a read-only hygiene report, safe review plan, or boundary route.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[556,559,562,565],{"name":557,"slug":558,"type":15},"Audit","audit",{"name":560,"slug":561,"type":15},"Compliance","compliance",{"name":563,"slug":564,"type":15},"Governance","governance",{"name":9,"slug":8,"type":15},"2026-08-11T04:26:29.395035",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":23,"repoUrl":24,"updatedAt":581},"search-performance-optimizer","optimize Splunk search performance","Diagnose and improve one existing functional Splunk search from supplied SPL and runtime evidence. Use when a search, report, dashboard panel, or scheduled search is slow, queued, expensive, resource-intensive, or prematurely finalized and the user needs evidence-backed query tuning, acceleration-fit analysis, workload separation, or a comparable before-and-after plan. Route new-search authoring, functional break\u002Ffix, governance, and deployment-wide operations to their owning workflows.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[573,576,579,580],{"name":574,"slug":575,"type":15},"Monitoring","monitoring",{"name":577,"slug":578,"type":15},"Performance","performance",{"name":21,"slug":22,"type":15},{"name":9,"slug":8,"type":15},"2026-08-15T03:47:41.141068",15,{"items":584,"total":582},[585,592,598,605,612,619,626,633,648,664,679,695],{"slug":483,"name":483,"fn":484,"description":485,"org":586,"tags":587,"stars":23,"repoUrl":24,"updatedAt":498},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[588,589,590,591],{"name":489,"slug":490,"type":15},{"name":492,"slug":493,"type":15},{"name":495,"slug":496,"type":15},{"name":9,"slug":8,"type":15},{"slug":500,"name":500,"fn":501,"description":502,"org":593,"tags":594,"stars":23,"repoUrl":24,"updatedAt":514},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[595,596,597],{"name":506,"slug":507,"type":15},{"name":509,"slug":510,"type":15},{"name":512,"slug":513,"type":15},{"slug":516,"name":516,"fn":517,"description":518,"org":599,"tags":600,"stars":23,"repoUrl":24,"updatedAt":527},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[601,602,603,604],{"name":489,"slug":490,"type":15},{"name":523,"slug":524,"type":15},{"name":495,"slug":496,"type":15},{"name":9,"slug":8,"type":15},{"slug":4,"name":4,"fn":5,"description":6,"org":606,"tags":607,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[608,609,610,611],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":21,"slug":22,"type":15},{"name":9,"slug":8,"type":15},{"slug":536,"name":536,"fn":537,"description":538,"org":613,"tags":614,"stars":23,"repoUrl":24,"updatedAt":549},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[615,616,617,618],{"name":542,"slug":543,"type":15},{"name":545,"slug":546,"type":15},{"name":495,"slug":496,"type":15},{"name":9,"slug":8,"type":15},{"slug":551,"name":551,"fn":552,"description":553,"org":620,"tags":621,"stars":23,"repoUrl":24,"updatedAt":566},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[622,623,624,625],{"name":557,"slug":558,"type":15},{"name":560,"slug":561,"type":15},{"name":563,"slug":564,"type":15},{"name":9,"slug":8,"type":15},{"slug":568,"name":568,"fn":569,"description":570,"org":627,"tags":628,"stars":23,"repoUrl":24,"updatedAt":581},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[629,630,631,632],{"name":574,"slug":575,"type":15},{"name":577,"slug":578,"type":15},{"name":21,"slug":22,"type":15},{"name":9,"slug":8,"type":15},{"slug":634,"name":634,"fn":635,"description":636,"org":637,"tags":638,"stars":23,"repoUrl":24,"updatedAt":647},"splunk-cloud-admin-copilot","manage Splunk Cloud IP allowlists","Read Splunk Cloud Platform ACS state, assess maintenance or restart readiness without changing it, and execute one explicitly approved IPv4 CIDR add or remove for one feature-specific IP allowlist through the documented public ACS provider. Use when a Cloud admin needs exact-target preflight, a minimal allowlist mutation, readback, rollback, and a sanitized receipt; route every other administration write and specialist domain.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[639,642,643,646],{"name":640,"slug":641,"type":15},"Cloud","cloud",{"name":495,"slug":496,"type":15},{"name":644,"slug":645,"type":15},"Security","security",{"name":9,"slug":8,"type":15},"2026-08-05T05:58:09.16516",{"slug":649,"name":649,"fn":650,"description":651,"org":652,"tags":653,"stars":23,"repoUrl":24,"updatedAt":663},"splunk-dashboard-converter","convert Splunk Simple XML to Dashboard Studio","Convert classic Splunk Simple XML dashboards (version 1) into Dashboard Studio (version 2). Takes classic Simple XML as input, preserves every SPL query verbatim, and returns the Studio JSON definition to the caller. Use when the user asks to convert, migrate, upgrade, modernize, port, or make a v2 \u002F Dashboard Studio version of an existing classic Splunk dashboard, form, or Simple XML view.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[654,657,660],{"name":655,"slug":656,"type":15},"Dashboards","dashboards",{"name":658,"slug":659,"type":15},"Migration","migration",{"name":661,"slug":662,"type":15},"XML","xml","2026-08-02T06:09:08.054477",{"slug":665,"name":665,"fn":666,"description":667,"org":668,"tags":669,"stars":23,"repoUrl":24,"updatedAt":678},"splunk-health-monitoring-and-diagnostic-collection","monitor Splunk health and diagnostics","Answer cited questions about Splunk Cloud Monitoring Console, Splunk Enterprise Monitoring Console, splunkd health reports, health dashboards, health.log, and health endpoints; collect and normalize health evidence; guide privacy-aware diag and RapidDiag collection; and interpret supplied health signals into bounded hypotheses and support handoffs. Use for Splunk Cloud Platform or Splunk Enterprise deployment-health signals and diagnostic artifacts, not broad incident root-cause analysis, HEC-specific troubleshooting, general SPL execution, cluster remediation, uploads, tickets, or environment changes.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[670,673,674,677],{"name":671,"slug":672,"type":15},"Diagnostics","diagnostics",{"name":574,"slug":575,"type":15},{"name":675,"slug":676,"type":15},"Observability","observability",{"name":9,"slug":8,"type":15},"2026-08-15T03:47:44.624133",{"slug":680,"name":680,"fn":681,"description":682,"org":683,"tags":684,"stars":23,"repoUrl":24,"updatedAt":694},"splunk-identity-saml-readiness-advisor","diagnose Splunk identity and SAML configurations","Research current public Splunk sources and use optional existing-auth read-only stack evidence to diagnose SAML, LDAP, roles, capabilities, group mappings, login failures, and access readiness without changing identity configuration or handling credentials.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[685,688,691,692,693],{"name":686,"slug":687,"type":15},"Access Control","access-control",{"name":689,"slug":690,"type":15},"Auth","auth",{"name":542,"slug":543,"type":15},{"name":644,"slug":645,"type":15},{"name":9,"slug":8,"type":15},"2026-08-08T04:19:14.673843",{"slug":696,"name":696,"fn":697,"description":698,"org":699,"tags":700,"stars":23,"repoUrl":24,"updatedAt":711},"splunk-product-question-navigator","answer Splunk product questions","Research and answer current Splunk product questions from public sources with explicit product, deployment, version, freshness, and evidence boundaries. Use for explanatory questions such as what a feature does, where it is available, which edition or version supports it, whether two products or versions are compatible, or what changed. Route live incidents, stack changes, SPL execution, account-specific decisions, and unpublished roadmap questions to their owning workflow.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[701,704,707,710],{"name":702,"slug":703,"type":15},"Documentation","documentation",{"name":705,"slug":706,"type":15},"Enterprise Search","enterprise-search",{"name":708,"slug":709,"type":15},"Research","research",{"name":9,"slug":8,"type":15},"2026-08-08T04:19:13.824528"]