Rootly Services — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Rootly Services (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The Rootly service catalog provides a centralized registry of all services in your infrastructure. Each service has ownership, tier classification, dependencies, and is linked to incidents and alerts. This enables rapid identification of affected components during incidents and accurate impact assessment.
Services are classified by business criticality:
Each service has:
Rootly tracks upstream and downstream dependencies:
rootly_list_servicesParameters:
team -- Filter by owning teamtier -- Filter by service tierenvironment -- Filter by environmentExample response:
{
"data": [
{
"id": "svc-001",
"type": "services",
"attributes": {
"name": "payment-service",
"slug": "payment-service",
"description": "Handles payment processing via Stripe",
"tier": "tier_1",
"owner": { "name": "Platform Team" },
"slack_channel": "#payment-service",
"status": "operational",
"incidents_count": 2,
"dependencies_count": 3
}
}
]
}rootly_get_serviceParameters:
service_id -- The service IDrootly_create_serviceParameters:
name -- Service name (required)description -- Service descriptiontier -- Service tierteam_id -- Owning team IDslack_channel -- Associated Slack channelrootly_update_serviceParameters:
service_id -- The service IDname -- Updated namedescription -- Updated descriptiontier -- Updated tierteam_id -- Updated owning teamrootly_list_services to get all servicesrootly_list_incidentsrootly_get_serviceCause: Invalid service ID or service deleted Solution: List services to verify the correct ID
Cause: Service with this name already exists Solution: Use a unique name or update the existing service
Cause: Tier value doesn't match configured tiers Solution: Use valid tier values (tier_1, tier_2, tier_3, tier_4)
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.