skills.rest
npow
npowCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

platform-friction-detector

Detect silent workarounds and friction in platform libraries from dependency removals, commits, and Slack.

4|Updated Feb 23, 2026
Search Tags:#static analysis#sourcegraph#dependency removal#platform friction#silent churn#workaround detection
One-click install
npx skills add https://github.com/npow/claude-skills --skill platform-friction-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-friction-detector
Source: https://github.com/npow/claude-skills/tree/main/platform-friction-detector
Command: npx skills add https://github.com/npow/claude-skills --skill platform-friction-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reveals silent user friction when downstream teams remove, replace, bypass, or work around platform libraries without filing issues, helping platform owners identify untracked churn and prioritize improvements.

Core Features & Use Cases

  • Dependency and Import Scanning: Detect removed platform dependencies, imports, and replacement implementations across downstream repositories.
  • Commit, Pull Request, and Slack Analysis: Gather contextual evidence about workarounds, dependency conflicts, missing features, performance issues, and breaking changes.
  • Root-Cause Reporting: Classify signals by type and severity, group related incidents by root cause, identify replacements, and deliver a structured friction report with all-clear coverage for unaffected packages.
  • Use Case: A platform team can scan its owned libraries across downstream repositories to discover teams replacing a storage abstraction with a lower-level client because of dependency conflicts, then use the evidence to guide remediation.

Quick Start

Use the platform friction detector to scan configured downstream repositories and Slack channels for the last 30 days, group the findings by root cause, and generate the friction report.

Frequently Asked Questions about platform-friction-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect silent user workarounds and downstream friction affecting platform libraries?▼

Detect silent user workarounds by scanning downstream repositories for dependency removals, import replacements, and commits, then analyzing pull requests and Slack discussions to group related incidents by root cause and deliver a structured friction report.

What is silent churn in platform engineering and how does it impact library adoption?▼

Silent churn occurs when downstream teams remove, replace, bypass, or work around platform libraries without filing issues. It impacts library adoption by hiding untracked friction from platform owners who need evidence to prioritize remediation.

Can I use Sourcegraph to scan downstream repositories for dependency removals and import replacements?▼

Yes, Sourcegraph integration collects evidence across configured downstream repository search scopes by scanning for removed platform dependencies, imports, and replacement implementations to identify teams bypassing platform libraries.

How do I monitor owned packages across downstream repositories for breaking changes and dependency conflicts?▼

Monitor owned packages by configuring platform packages and repository search scope, then gathering contextual evidence from commits, pull requests, and Slack channels about dependency conflicts, missing features, performance issues, and breaking changes.

Does the platform friction detector require Slack channels and GitHub integrations to generate a friction report?▼

It requires configured platform packages, repository search scope, and Sourcegraph integration, plus optional replacement patterns, Slack channels, GitHub, and HTML delivery integrations to collect evidence and produce a grouped friction report.

What is the best way to classify platform friction signals by type and severity for root-cause analysis?▼

The best way to classify platform friction signals is to group related incidents by root cause, identify replacement implementations, classify signals by type and severity, and deliver a structured report with all-clear coverage for unaffected packages.

Related Skills

Explore More Software Engineering Skills→
npownpow
4

dependency-audit

Audit dependency health and security signals across configured repositories.

Community
Advanced
TruCol270TruCol270
1

gsd-forensics

Diagnose failed GSD workflows and generate forensic reports from git history.

Community
Advanced
IndustrialIndustrial

code-reviewer

Analyze code for security vulnerabilities and performance issues.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

dependency-conflict-resolver

Detect and resolve dependency conflicts across npm, pip, cargo, and composer.

Community
Advanced