Reserved for the SKILL.SCH open source community.\n\nA single resource can legitimately trigger more than one check right now (e.g. a VM could show up in both stopped_not_deallocated_vms and untagged_resources if it's stopped-but-billing AND missing tags). Each finding is currently independent in findings.json, which is correct when the underlying issues are genuinely separate, but there's no way to see 'this one resource has N findings against it' as a rolled-up view — useful for prioritizing which resource to fix first.\n\nGood scope: a new cloudcost findings summary command (or a flag on findings list) that groups by resource_id and shows total combined impact per resource.
Reserved for the SKILL.SCH open source community.\n\nA single resource can legitimately trigger more than one check right now (e.g. a VM could show up in both
stopped_not_deallocated_vmsanduntagged_resourcesif it's stopped-but-billing AND missing tags). Each finding is currently independent infindings.json, which is correct when the underlying issues are genuinely separate, but there's no way to see 'this one resource has N findings against it' as a rolled-up view — useful for prioritizing which resource to fix first.\n\nGood scope: a newcloudcost findings summarycommand (or a flag onfindings list) that groups byresource_idand shows total combined impact per resource.