agentsclimarketplace
Sign in

Byte research

Skill elan6666/your-bytedance-skills/byte-research

Research competitors, alternatives, pricing, market trends, user complaints, and product opportunities for Your ByteDance / Byte OS. Use when the user asks for competitor benchmarking, market intelligence, online research, product iteration based on external signals, or refreshed research for an existing `.byte-os/` project.From its SKILL.md

Install
npx -y skills add elan6666/your-bytedance-skills --skill byte-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 532 tokens by cl100k_base, as published. Nobody here has run it

Byte Research

Research supplies the external world signal for Your ByteDance. It must use current sources for market, competitor, pricing, and trend claims.

Required Behavior

Browse the web when researching modern products, competitors, pricing, market trends, app reviews, changelogs, or "latest" activity. Cite sources with links in the output artifacts.

Prefer:

  • Official product pages
  • Docs and changelogs
  • Pricing pages
  • App store listings and reviews
  • Public roadmaps
  • Credible industry articles
  • GitHub repositories for developer tools

Avoid unsupported claims, stale assumptions, and invented user feedback.

Workflow

  1. Read current context:
.byte-os/BYTE.md
.byte-os/STATUS.md
.byte-os/PRODUCT_SPEC.md
.byte-os/ROADMAP.md
  1. Identify research questions:
  • What products solve the same problem?
  • What adjacent tools are substitutes?
  • How do competitors price and package value?
  • What are users praising or complaining about?
  • What features are becoming table stakes?
  • Where is there room for differentiation?
  • Which assumptions in OKRS.md need evidence?
  1. Search and compare:
  • Direct competitors
  • Indirect substitutes
  • Adjacent workflow tools
  • Open-source or low-cost alternatives
  • Pricing and packaging
  • Onboarding and activation patterns
  • Recent product updates
  1. Synthesize:
  • Keep facts separate from inference.
  • Convert findings into product implications.
  • Mark "copy", "adapt", "avoid", and "differentiate" opportunities.
  • Record confidence level and evidence quality.
  • Prefer direct product evidence over commentary when available.

Artifacts

Write or update:

.byte-os/RESEARCH.md
.byte-os/COMPETITORS.md
.byte-os/DECISIONS.md
.byte-os/STATUS.md

COMPETITORS.md should include:

| Product | Positioning | Key features | Pricing | Strength | Weakness | Source |

RESEARCH.md should include:

  • Research date
  • Search scope
  • Key findings
  • User complaint patterns
  • Product opportunities
  • Risks and caveats
  • Recommended impact on roadmap

Update STATUS.md using the shared Byte OS state contract with stage: researched, current_workflow: byte-research, and the next safe workflow derived from the shared state resolver.

Completion Criteria

Research is complete when the next product decision can name what the market already does, what users seem to value, and where this product should be different.

What ships with it: 1 file

223 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most research analysis skills give in 532 tokens

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

  • Generate a markdown reportin 32 of 1063, across 23 files
  • Cite each claim's sourcein 30 of 1063, across 15 files
  • Define the ideal customer profilein 20 of 1063, across 2 files
  • Search for companies matching the criteriain 20 of 1063, across 2 files
  • Assign a fit score from one to tenin 20 of 1063, across 2 files
  • Analyze the codebase to understand the productin 19 of 1063, across 1 file
  • Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
  • Look for signals of immediate needin 19 of 1063, across 1 file
  • Identify the target decision maker rolein 19 of 1063, across 1 file
  • Suggest a personalized contact strategyin 19 of 1063, across 1 file
  • Provide conversation starters for outreachin 19 of 1063, across 1 file
  • Format results in a scannable markdown templatein 19 of 1063, across 1 file

Said here and by no other author read

  • browse the web for current market claims
  • cite sources with links in output artifacts
  • prefer official product pages and changelogs
  • identify research questions about the market
  • record confidence level and evidence quality
  • write the competitors comparison table

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.