olares-settings

Read and mutate Olares Settings areas with role-based access checks.

5.2k|320|Updated Apr 29, 2024
One-click install
npx skills add https://github.com/beclab/Olares --skill olares-settings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: olares-settings
Source: https://github.com/beclab/Olares/tree/main/cli/skills/olares-settings
Command: npx skills add https://github.com/beclab/Olares --skill olares-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads and mutates Olares Settings from the CLI, aligning actions with the active profile to enforce role-based access and auditable activity directly from the command line.

Core Features & Use Cases

  • Exposes 13 settings areas (users, appearance, apps, integration, vpn, network, gpu, video, search, backup, restore, advanced, and me) mirroring the SPA’s Settings surface.
  • Supports both read-only and mutating verbs, with soft preflight checks to ensure proper permissions before attempting changes.
  • Use cases include administrators auditing and configuring system preferences, and regular users performing guided inquiries and allowed mutations via safe verbs.

Quick Start

Begin by checking your active profile with the CLI and then explore a Settings area to see your privileges and available actions.

Frequently Asked Questions about olares-settings

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

FAQPage Schema
How do I manage Olares settings from the command line?

The CLI reads the active profile to enforce role-based access and cache identity while exposing read-only and mutating verbs across 13 settings areas. It covers users, appearance, apps, integration, vpn, network, gpu, video, search, backup, restore, advanced, and me.

Can I configure Olares user roles and VPN settings via CLI?

You can configure Olares user roles and VPN settings via CLI by operating across 13 settings area sub-trees including users and vpn. The tool supports both read-only inquiries and allowed mutations through safe verbs aligned with your active profile.

How does role-based access work for Olares CLI operations?

Role-based access for Olares CLI operations works by reading the active profile and implementing token refreshes before executing commands. Soft preflight guards ensure you have proper permissions before attempting any configuration changes.

What is a soft preflight check in Olares settings automation?

A soft preflight check in Olares settings automation is a guard that verifies proper permissions before attempting changes. It ensures safe, auditable operations by validating role-based access prior to running mutating verbs against per-area endpoints.

Does the Olares settings CLI support token refresh automatically?

Yes, the Olares settings CLI supports token refresh automatically. It implements token refresh and role checks to provide safe, auditable operations directly from the command line without requiring manual re-authentication for per-area endpoints.

What are the limitations of using CLI for Olares settings configuration?

Limitations of using CLI for Olares settings configuration include dependency on per-area endpoints and frontmatter-driven metadata for discovery. Mutations are constrained by role-based access and soft preflight permission guards tied to the active profile.