get-started

Guide users through initial setup and a Chrome DevTools demonstration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/acedergren/oci-self-service-portal --skill get-started-acedergren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-started
Source: https://github.com/acedergren/oci-self-service-portal/tree/main/.opencode/skills/get-started
Command: npx skills add https://github.com/acedergren/oci-self-service-portal --skill get-started-acedergren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding and setup are simplified by guiding users through the initial configuration and a Chrome DevTools demonstration, reducing setup friction and time-to-value.

Core Features & Use Cases

  • Step-by-step onboarding flow to configure a new environment.
  • Demonstrated Chrome DevTools workflow to showcase debugging and inspection.
  • Deterministic, four-line response to user prompts for consistent outcomes.

Quick Start

Follow the get-started flow to set up your environment and run the Chrome DevTools demo.

Frequently Asked Questions about get-started

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a new environment for a Chrome DevTools workflow?

To set up a new environment for a Chrome DevTools workflow, you can follow a guided onboarding flow that configures tooling and demonstrates debugging, reducing initial setup friction and time-to-value.

What is the best way to get started with onboarding and configuring Chrome DevTools?

The best way to get started with onboarding is by using a guided configuration flow that walks through the initial tool setup and runs a Chrome DevTools demonstration to showcase debugging and inspection capabilities.

Does the Chrome DevTools onboarding flow require any specific integrations?

Yes, the Chrome DevTools onboarding flow requires access to a Chrome DevTools MCP integration to successfully guide the setup and execute the demonstration workflow.

How does the deterministic reply format work in onboarding workflows?

The deterministic reply format works by providing a consistent four-line response to user prompts during the onboarding workflow, ensuring predictable and standardized outcomes for environment configuration.

Can I use this onboarding flow to demonstrate debugging and inspection?

Yes, you can use this onboarding flow to demonstrate debugging and inspection, as it includes a specific Chrome DevTools workflow designed to showcase these exact capabilities.

What are the limitations of using a fixed four-line response for environment setup?

The limitation of using a fixed four-line response for environment setup is that the deterministic format restricts output to exactly four lines, which may limit detailed explanations during complex configuration scenarios.