AI Agent Hub
Back to skills
OPC One-Person Company Knowledge Agent Suite icon

OPC One-Person Company Knowledge Agent Suite

Business Operations Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @user_173b32ba/opc-knowledge-agent-suite-cn into your AI assistant following the guide at https://skillhub.cn/install/skillhub.md.

About this skill

What problem it addresses

Early one-person company projects often sit on scattered materials: market notes, policy pages, technical sources, competitors, and competition requirements. The gap is not more text, but a structure that turns those notes into decisions: whether to build, first landing scenario, first users, MVP, and risk. This suite targets that founder workflow with decision-driven, auditable outputs.

How it works

  • Routed decomposition: 00_orchestrator decides which modules to load instead of forcing a final report.
  • Material and evidence handling: 02_document_ingestion plans summaries, chunking, and storage fields; evidence is scored on authority, recency, relevance, specificity, and cross-validation, with weak evidence never supporting conclusions alone.
  • Business and product planning: 04_strategic_intelligence maps PESTEL gaps, 05_scenario_matching selects the first landing scenario, 06_user_persona clarifies users and decision chain, 07_business_model tests risky assumptions, and 08_mvp_roadmap produces a minimal validation plan.
  • Safety boundary: it does not run local commands, open listening services, or request keys, tokens, or cookies; when evidence is missing it outputs missing_information and manual fallback steps.

Where it fits

It is suitable for startup competitions, technology transfer, early-stage business hypotheses, and project knowledge base planning. It is not a substitute for legal, IP, financial, or market due diligence; high-risk claims about policy, licensing, IP, and compliance should be marked as pending verification.

Use Cases

  • Before a startup competition, organize technical sources, policy notes, and competitor materials into a citable entry report
  • During project review, break market, user, and business assumptions into PESTEL gaps and an MVP validation plan
  • Before technology transfer, identify patent, licensing, public-material, and compliance risks, then output a verification checklist
  • During pitch preparation, combine document summaries, evidence scores, and task boards into an auditable pitch deck

Best For

  • One-person company founders who need to judge whether a project is worth pursuing and define the first scenario and MVP assumptions
  • Technology transfer leads who need to verify technical provenance, licensing boundaries, and IP compliance risks
  • Startup competition participants who need to turn scattered materials into evidence-backed competition reports
  • Early-stage product or operations roles who need to plan knowledge bases, workspace structure, and staged task boards