Competitive pricing & feature analysis — 14 direct auto-dealership AI agent / workflow competitors
npx skills add jgille07/dealertasker-competitive-analysisCompetitive pricing & feature analysis — 14 direct auto-dealership AI agent / workflow competitors
Source: https://github.com/jgille07/dealertasker-competitive-analysis
Discovered from GitHub repositories pushed in the last 24 hours for agent skills, Claude/Codex/Gemini workflows, MCP tooling, and adjacent AI-agent automation.
Native Claude Code + Codex skills for AI security review. Also ships instruction files for Cursor, Copilot, and Windsurf. Checks 33 risks: OWASP LLM Top 10 2025 · applied RAG/MCP/agent checks · OWASP Agentic 2026.
Enhance research paper writing by organizing workflows, improving structure, and supporting self-review for clear, logical, and well-aligned content.
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," or "qualified leads." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.
Claude Code plugin marketplace for the Adva platform — MCP + skills.
Unity MCP acts as a bridge, allowing AI assistants (like Claude, Cursor) to interact directly with your Unity Editor via a local MCP (Model Context Protocol) Client. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.