my-fetch-tweet▌
ai-native-camp/camp-1 · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Fetch X/Twitter tweets with summaries, insights, and full Korean translations via a three-stage pipeline.
- ›Extracts tweet text, author info, and engagement metrics (likes, retweets, views) using the FxEmbed API without JavaScript execution
- ›Supports multiple URL formats: x.com, twitter.com, fxtwitter.com, and fixupx.com
- ›Delivers insights in three stages: concise summary with author context, three-point analysis (core message, industry implications, personal relevance), then full natura
My Fetch Tweet
X/Twitter URL에서 트윗 원문, 작성자 정보, 인게이지먼트 데이터를 가져오고 요약-인사이트-전체 번역 3단계 파이프라인으로 제공하는 스킬.
API 연동 — FxEmbed
FxEmbed 오픈소스 프로젝트의 API (api.fxtwitter.com)를 활용한다.
JavaScript 없이 트윗 데이터를 추출할 수 있다.
URL 변환 규칙
- URL에서
screen_name과status_id를 추출한다 - 도메인을
api.fxtwitter.com으로 변환한다 - WebFetch로 JSON 데이터를 가져온다
https://x.com/garrytan/status/123456
→ https://api.fxtwitter.com/garrytan/status/123456
지원 URL 형식
x.com, twitter.com, fxtwitter.com, fixupx.com
API 응답 주요 필드
| 필드 | 설명 |
|---|---|
tweet.text |
트윗 본문 (URL 확장됨) |
tweet.author |
작성자 (name, screen_name, bio, followers) |
tweet.likes / retweets / replies / views |
인게이지먼트 수치 |
tweet.created_at |
작성 일시 |
tweet.media |
첨부 미디어 (photos, videos) |
tweet.quote |
인용 트윗 (동일 구조) |
번역 파이프라인 — 3단계
전체 번역을 바로 보여주지 않는다. 단계별로 제공하여 이해도를 높인다.
1단계: 요약 (3-5문장)
- 트윗의 핵심 주장을 한국어로 요약
- 작성자 정보 포함 (이름, 팔로워 수)
- 인게이지먼트 수치 포함 (좋아요, 리트윗, 조회수)
- "이 트윗이 뭘 말하는지 30초 만에 파악"
2단계: 인사이트 (3개)
- 핵심 메시지: 이 트윗이 정말 말하고 싶은 것
- 시사점: 업계/트렌드에서의 의미
- 적용점: 나(독자)에게 어떤 의미인지
3단계: 전체 번역
- 원문 전체를 자연스러운 한국어로 번역
- 인용 트윗이 있으면 함께 번역
- 전문 용어는 원문 병기 (예: "에이전트(Agent)")
WebFetch Fallback
스크립트 실행이 어려운 경우 WebFetch 도구로 직접 API 호출 가능:
URL: https://api.fxtwitter.com/{screen_name}/status/{status_id}
Prompt: "Extract the full tweet text, author name, and engagement metrics"
Limitations
- 비공개 계정 트윗은 조회 불가
- 삭제된 트윗은 조회 불가
- API rate limit은 FxEmbed 서버 정책에 따름
How to use my-fetch-tweet on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add my-fetch-tweet
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches my-fetch-tweet from GitHub repository ai-native-camp/camp-1 and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate my-fetch-tweet. Access the skill through slash commands (e.g., /my-fetch-tweet) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★75 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
Registry listing for my-fetch-tweet matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noor Thomas· Dec 20, 2024
Registry listing for my-fetch-tweet matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Nikhil Abbas· Dec 16, 2024
Keeps context tight: my-fetch-tweet is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Fatima Taylor· Dec 16, 2024
my-fetch-tweet is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Isabella Menon· Dec 16, 2024
my-fetch-tweet fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Nikhil Park· Dec 12, 2024
Useful defaults in my-fetch-tweet — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Luis Shah· Dec 8, 2024
my-fetch-tweet is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mateo Thomas· Dec 8, 2024
Solid pick for teams standardizing on skills: my-fetch-tweet is focused, and the summary matches what you get after install.
- ★★★★★Anika Lopez· Dec 4, 2024
my-fetch-tweet reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Luis Kapoor· Nov 27, 2024
Registry listing for my-fetch-tweet matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 75