경쟁-분석은(는) 무엇을 하나요?
사용자가 경쟁사를 이해하고 대응할 수 있도록 돕습니다. 경쟁사 대비 포지셔닝, 시장 위협 평가, 경쟁 워 게임 실행, 또는 경쟁사와 고객 중 어디에 집중할지 결정할 때 사용하세요.
사용자가 경쟁사를 이해하고 대응할 수 있도록 돕습니다. 경쟁사 대비 포지셔닝, 시장 위협 평가, 경쟁 워 게임 실행, 또는 경쟁사와 고객 중 어디에 집중할지 결정할 때 사용하세요.
이 스킬은 경쟁 분석을 수행하는 AI 에이전트를 위한 도구로, 사용자가 경쟁사를 체계적으로 이해하고 전략적으로 대응할 수 있도록 지원합니다. 주요 사용 사례로는 경쟁사 대비 제품 포지셔닝, 시장 위협 평가, 경쟁 워 게임 시뮬레이션, 그리고 경쟁사와 고객 간 리소스 배분 결정 등이 포함됩니다. 다양한 AI 에이전트 플랫폼(Claude Code, Cursor, Codex 등)과 호환되며, SKILL.md 문서를 기반으로 에이전트가 경쟁 분석 관련 작업을 수행할 때 필요한 컨텍스트와 지침을 제공합니다. 이 스킬을 통해 AI 에이전트는 경쟁 환경을 분석하고, 경쟁사의 강점과 약점을 파악하며, 효과적인 대응 전략을 수립하는 데 도움을 줄 수 있습니다.
npx skills add https://github.com/refoundai/lenny-skills/tree/main/skills/competitive-analysisInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
사용자가 경쟁사를 이해하고 대응할 수 있도록 돕습니다. 경쟁사 대비 포지셔닝, 시장 위협 평가, 경쟁 워 게임 실행, 또는 경쟁사와 고객 중 어디에 집중할지 결정할 때 사용하세요.
This repo contains 20 individual skills — each has its own dedicated page.
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.
Help users build effective AI applications. Use when someone is building with LLMs, writing prompts, designing AI features, implementing RAG, creating agents, running evals, or trying to improve AI output quality.
Help users navigate career changes and pivots. Use when someone is considering a new role, transitioning into product management, evaluating job offers, taking a sabbatical, or feeling stuck in their current position.
Help users develop and coach product managers. Use when someone is managing PMs, creating development plans, running performance reviews, or trying to level up their PM team's capabilities.
Help users build and grow product communities. Use when someone is starting a community, scaling an ambassador program, driving community-led growth, or choosing between user, developer, or partner communities.
Help users conduct effective hiring interviews. Use when someone is designing an interview loop, crafting interview questions, evaluating candidates in real-time, or building a structured interview process.
Help users run better customer and user interviews. Use when someone is preparing for user research, planning discovery interviews, writing interview questions, analyzing interview findings, or trying to understand customer needs.
Help users build content marketing strategies. Use when someone is starting a blog, building SEO, creating thought leadership content, or deciding on content formats and distribution channels.
Help users work effectively across functions. Use when someone is navigating PM-engineering relationships, resolving cross-team conflicts, building product trios, or improving handoffs between design, engineering, and product.
Help users create compelling product visions. Use when someone is writing a vision statement, defining a long-term product direction, aligning teams on the future state, or distinguishing vision from strategy.
Help users delegate effectively. Use when someone is struggling to let go of tasks, deciding what to delegate, building team autonomy, or balancing being hands-on vs hands-off.
Help users understand and build design engineering capabilities. Use when someone is creating a design engineering function, hiring design engineers, or bridging the gap between design and engineering teams.
Help users design and optimize growth loops. Use when someone is building viral mechanics, designing referral programs, creating product-led acquisition, or figuring out how to make their product grow itself.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.