Skip to content

Skills suchen.../

Agent Skill Search Engine

Suche

Suche
Kategorien
Berufe

About

About
Privacy
Terms

© 2026 Skills Pool. Alle Rechte vorbehalten.

Car Comparison | Skills Pool

Skill-Datei

Car Comparison

Compare car variants or different car models using specifications, ownership experience, and narrative evidence.

granitebps0 Sterne04.04.2026

Beruf
Kategorien: Debugging

Skill-Inhalt

Car Comparison Skill

Use this skill when the user wants to compare vehicles. Supports two comparison modes.

Use English field labels in comparison matrices, but prioritize Indonesian sources and Indonesian owner reviews.

Comparison Modes

Mode 1: Variant Comparison (same model)

Compare trims or variants of the same car model.

Output file: {car-name}-variant-comparison.md
Location: Inside research/{car-name}/
Example: Stargazer Cartenz Smart vs Cartenz Prime vs Cartenz X Trend

Mode 2: Cross-Car Comparison (different models)

Compare two or more different car models against each other.

Output file: {car1-name}-vs-{car2-name}-comparison.md
Location: Inside root (not inside a car-specific folder)

Verwandte Skills

Schnellinstallation

Car Comparison

npx skillvault add granitebps/granitebps-cars-review-github-skills-car-comparison-skill-md

Skill herunterladen Repository öffnen

Autor: granitebps
Sterne: 0
Aktualisiert: 04.04.2026
Beruf

Auf dieser Seite

01Car Comparison Skill

research/

Example: Hyundai Stargazer vs Toyota Veloz vs Mitsubishi Xpander

Interactive Clarification

You may ask the user clarifying questions to produce a more targeted comparison:

What is your budget range?
What are your top priorities? (comfort, safety, fuel economy, resale, etc.)
What is your primary use case? (city, toll, long-distance, mudik)
Are there specific features you care about? (ADAS, 360 camera, captain seat, etc.)
How many passengers do you typically carry?

Keep questions concise. Do not ask more than 5 clarifying questions.

Comparison Using Both Information Types

Compare using both Specification and Narrative:

Specification: Side-by-side tables of facts (price, dimensions, features, ADAS)
Narrative: Commentary comparing real-world experiences (comfort, reliability, service, owner satisfaction)

Comparison Factors

Compare each relevant variant, not just the model name.

Focus on:

price per variant
release timing
dimensions
ground clearance
luggage capacity
tank capacity
engine performance
fuel efficiency
transmission
suspension and suspension character
tires and wheel setup
comfort and NVH
hill-climbing ability
reliability
annual tax
maintenance cost
after-sales support
spare-part availability
resale value
interior comfort
safety features
technology features
ADAS availability by variant
owner feedback quality and consistency

Method

Gather structured specifications of each vehicle by variant.
Map branded ADAS features into common categories while preserving original names.
Identify strengths and weaknesses by variant.
Compare ownership cost, annual tax, after-sales support, and spare parts.
Analyze reviewer opinions using Narrative evidence.
Analyze owner feedback using Narrative evidence.
Capture any additional related information that materially affects buying decisions.

Output Format

Use structured comparison tables for Specification. Use commentary prose for Narrative comparisons.

Include sections:

Variant matrix (side-by-side table)
Specifications comparison
Pros and cons per option
Reviewer insights (Narrative)
Owner feedback with sources (Narrative)
Final recommendation with winner per category

02

Comparison Modes

03Mode 1: Variant Comparison (same model)

04Mode 2: Cross-Car Comparison (different models)

05Interactive Clarification

06Comparison Using Both Information Types

07Comparison Factors

09Output Format

Automotive Service Technicians and Mechanics

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Automotive Service Technicians and Mechanics