Auto Repair Shop Operations
v1.0.0Provides benchmarks, compliance, technician pay, parts markup, KPIs, startup costs, and growth guidance for independent auto repair shop operations.
⭐ 0· 343·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (auto repair shop operations) match the provided SKILL.md and README content. The skill is purely advisory (benchmarks, KPIs, compliance, costs) and does not request credentials, binaries, or config access. Note: the skill's provenance is unclear (source/homepage not provided and owner ID is opaque), which affects trust but not functional coherence.
Instruction Scope
SKILL.md contains static operational guidance, tables, and checklists. It does not instruct the agent to read local files, access environment variables, call external endpoints, or exfiltrate data. README contains links to external resources (afrexai-cto.github.io) but SKILL.md itself stays within the stated scope.
Install Mechanism
No install spec and no code files — instruction-only, so nothing is written to disk or downloaded. This is the lowest-risk install profile and is proportionate to the skill's advisory purpose.
Credentials
The skill declares no required environment variables, credentials, or config paths. That aligns with an informational/consulting skill and is proportionate.
Persistence & Privilege
always is false, user-invocable is true, and the skill does not request persistent system privileges. There is no indication it modifies other skills or system settings.
Scan Findings in Context
[no-findings] expected: The regex scanner had no code files to analyze (instruction-only skill). Absence of findings is expected for a purely textual guidance skill.
Assessment
This skill appears coherent and purely informational. Before installing or relying on it: (1) verify the publisher/website (provenance is unclear), (2) do not provide any credentials to the skill (none are required), (3) treat the external README links as third-party resources and review them separately (they may lead to paid products), and (4) verify regulatory figures (EPA/OSHA penalties, certification requirements) against official local sources before acting on them.Like a lobster shell, security has layers — review code before you run it.
auto repairvk97dgrr72db5w4q7sam52mfwa5821ewkautomotivevk97dgrr72db5w4q7sam52mfwa5821ewklatestvk97dgrr72db5w4q7sam52mfwa5821ewkmechanicvk97dgrr72db5w4q7sam52mfwa5821ewkoperationsvk97dgrr72db5w4q7sam52mfwa5821ewk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.