Results for “startup”

吉里吉里Z (krkrz) の SDL3 / WINVER ビルドを REPL 経由でエージェントから駆動するためのリファレンス。krkrz を起動して TJS スクリプトを評価・検証・デバッグする、startup.tjs を介さず明示的に処理を開始する、入力イベント (キー/マウス) を注入する、画面をキャプチャして目視確認する、Elements ダイアログを観測・操作する、例外やダイアログ表示をコンソールで観測する、コアデモ全シーンを自動巡回してキャプチャで表示確認する (-demotest / -demotestcap)、といった場面で使う。**外部エージェントは console(CONIN$) に打てないので -replfile ファイルチャネルが本命**。起動フラグ (-repl / -replfile / -nostartup / -loglevel / -display / -ignoremouse)、ファイルチャネルのプロトコル、Agent API (入力注入 / captureScreen / dialogs / dialogClick)、ドットコマンド (.cap/.dlg/.click/.mem 等)、REPL 駆動時の挙動変更 (例外で即終了しない / inform と例外ダイアログがコンソールに出る) を網羅。TJS2 言語仕様そのものは skill `tjs2`、本体クラス API は skill `krkrz` を参照。

The English summary is being prepared. Showing the original description.

Guide a startup to set a single quantified traction goal and define the critical path of milestones to reach it. Use whenever a founder needs to prioritize activities, set growth goals, define milestones, decide what NOT to work on, plan quarterly/yearly execution, cascade goals to teams, escape the 'too many things to do' trap, or apply a binary on-path/off-path filter to proposed work. Activates on phrases like 'traction goal', 'critical path', 'what should we focus on', 'too many priorities', 'prioritization', 'milestones', 'quarterly planning', 'yearly goals', 'OKRs', 'where should I spend my time', 'what NOT to do', 'company planning', 'goal setting', 'DuckDuckGo', 'roadmap'.

The English summary is being prepared. Showing the original description.

Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use PROACTIVELY when the user asks about market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics, or business strategy for pre-seed through Series A startups.

The English summary is being prepared. Showing the original description.

Plan and run pre-release checks for OpenClaw plugins, covering installation, removal, configuration repair, startup, external plugin compatibility, and packaged releases. Record test evidence, failures, and skipped checks to show what has been verified.

• Checking bundled plugin installation and removal before release
• Testing a beta package in a clean environment
• Verifying configuration repair and gateway startup

Rework a messy startup presentation into a coherent HTML slide deck for decision makers. Organize the narrative and evidence, then apply a consistent visual system of pastel-neon blocks, bold black borders, and coordinated layouts.

• Rework a startup deck for a board meeting
• Create agency credentials slides
• Present a brand redesign for review

Review a Homecore server operation plan before startup. Check authentication, restoration order, feature tests, speech provider configuration, and handling of pairing secrets. The skill reviews the plan without starting the server.

• Review a Homecore server startup plan
• Check restoration order and bounded limits
• Verify feature tests before enabling Wasmtime or HAP

Prepare and launch nf-core/pacsomatic workflows for matched tumor and normal PacBio HiFi samples. Generate sample sheets and launch files from unaligned BAM inputs, run local checks, submit cluster launchers, and troubleshoot startup failures.

• Prepare sample sheets for matched tumor and normal samples
• Review generated launch files with a dry run
• Submit a Nextflow launcher to a computing cluster

Plan startup hiring from pre-seed through Series A. Organize roles, reporting lines, salaries, and equity compensation, then estimate staffing costs and hiring timelines around revenue goals, funding milestones, and budget limits.

• Prioritizing the next startup hires
• Budgeting staffing costs, including benefits and overhead
• Planning salary and equity ranges

Build three- to five-year financial projections for early-stage startups, linking revenue, expenses, hiring, and cash balances. Compare conservative, base, and optimistic scenarios, estimate how long cash will last, and model fundraising amounts and ownership dilution.

• Build three- to five-year financial projections
• Estimate monthly cash use and remaining operating time
• Compare conservative, base, and optimistic scenarios

Audit GitHub Codespaces startup time and spending, then identify up to three evidence-based improvements to development containers, machine sizes, prebuilds, or idle timeouts, with validation results and expected impact.

• Investigating slow Codespaces startup
• Reviewing Codespaces spending
• Trimming unused development container components

Develop a product or side-project idea through guided questions and premise checks. Startup discussions examine evidence of demand, while builder discussions explore possibilities and scope, producing a design document before implementation begins.

• Examining demand for a startup idea
• Defining the smallest useful internal project
• Shaping a hackathon or side-project idea

Diagnose unreachable or unhealthy OpenShell gateways and sandbox startup failures. Identify the underlying execution platform, then examine logs, authentication, certificates, and configuration with the matching tools to narrow down the cause.

• Investigate gateway connection and health check failures
• Find why a sandbox remains pending or fails to start
• Check Docker or Podman runtime and image problems

Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.

• Create reusable startup context for an agent role
• Refresh an agent workspace from an existing starter
• Check a starter’s source history and freshness

Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.

• Designing an implementation and QA pair
• Creating a team with development and independent review
• Writing role guidance and team collaboration rules

Investigate local Rust services by starting the crate’s executable with debug logging and following its log output. Use the recorded messages to examine startup problems, runtime behavior, and errors while discussing findings with the agent.

• Investigating service startup problems
• Checking runtime behavior through logs
• Examining errors with an agent

Profile JAX, Levanter, or Marin training to investigate slow startup, compilation, initialization, or throughput. Turn execution traces, recorded timing events, into structured reports, identify costly operations, and compare performance before and after a bounded change.

• Investigate slow training startup or compilation
• Identify costly operations and communication delays
• Compare training performance before and after a change

Investigate code failures, startup problems, and performance regressions involving JAX, Iris, Zephyr, or TPU hardware. It guides failure reproduction, focused hypothesis testing, and infrastructure diagnosis using the relevant operational procedures.

• Investigating a reproducible code failure
• Diagnosing stuck Iris jobs
• Investigating slow Zephyr pipelines

Deep competitive intelligence for any market. Analyzes competitors' products, pricing, customer sentiment, GTM strategy, and growth signals using real web data. Produces battle cards, pricing landscape, and feature matrix. Use when the user wants to understand their competitive landscape, analyze competitors, compare products in a market, or research who they're competing against. Triggers for "who are my competitors", "competitive analysis", "competitor research", "battle cards", "pricing comparison", "competitor pricing", "market players", "competitive intelligence", "competitive landscape", "who else is in this space", "competitive moat", or any request to profile, compare, or map competitors in a category. Works standalone — no prior startup-design session needed.

The English summary is being prepared. Showing the original description.

Deprecated compatibility entry for Startup Program Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Startup Program Page.

The English summary is being prepared. Showing the original description.

Bringing up a complete ROS2 system on a robot's onboard computer: systemd services, launch file composition, ordered startup, and production monitoring. Use this skill when configuring a robot to start ROS2 nodes on boot, writing systemd unit files for ROS2 launch, composing layered launch files for full robot stacks, setting up watchdog monitoring, configuring udev rules for deterministic device naming, or debugging boot-time race conditions. Trigger whenever the user mentions robot bringup, robot startup, systemd for ROS2, ROS2 on boot, launch file composition, robot boot sequence, udev rules for cameras or serial ports, automatic restart for ROS2 nodes, network configuration for multi-machine ROS2, log rotation for robots, graceful shutdown of robot stacks, or SSH-based remote debugging. Also trigger for sourcing workspaces in systemd, ordered startup with health checks, or running ROS2 systems as long-running production services. Covers systemd on Ubuntu 22.04/24.04 with ROS2 Humble, Iron, and Jazzy.

The English summary is being prepared. Showing the original description.

Research startups and emerging companies with funding data, team composition, product positioning, market traction, and news coverage. Combines Apollo firmographics, LinkedIn team data, and web intelligence for comprehensive startup due diligence.

The English summary is being prepared. Showing the original description.

Core marketing principles for startups. Covers positioning, messaging, channels, and growth. Focus on what works for resource-constrained teams. Battle scars included: I've watched startups burn $1M on Instagram ads because "that's where competitors are", seen "growth hacks" destroy brand trust overnight, and advised founders who scaled marketing before finding product-market fit. Contrarian take: Most startup marketing advice is backwards. The best marketing doesn't feel like marketing. Distribution comes before product features. And your first 100 customers should never come from paid ads. Use when "marketing strategy, positioning, messaging, customer acquisition, growth channels, brand, go-to-market, " mentioned.

The English summary is being prepared. Showing the original description.

Analyze startups with Paul Graham mindset (pressure, founder-market fit, brutal validation), Dan Koe discipline (monetization, offer, distribution, sales), and Seth Godin principles (differentiation, narrative, smallest viable audience). Triggers on startup idea, business validation, MVP, first customers, revenue model, GTM, product-market fit, "I have an idea".

The English summary is being prepared. Showing the original description.

Marketing playbook for bootstrapped startups with zero budget. Covers organic-only channels including SEO, community building, social media, and word-of-mouth tactics that cost nothing but time. Follow @WeiYipei on X.

The English summary is being prepared. Showing the original description.