CtrlK
BlogDocsLog inGet started
Tessl Logo

plant-store-custom-commands

How to author custom commands for the plant-store CLI using the co-generated SDK.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/oauth-client-credentials-openapi/with-wire-tests/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Custom Commands for plant-store

Overview

The plant-store CLI supports user-authored custom commands that are compiled into the binary alongside the auto-generated API commands. Custom commands get a fully-wired SDK client that inherits the CLI's auth, retries, TLS, base URL, and global headers — zero configuration required.

Architecture

cli/plant-store/custom.rs    ← Your command handlers (protected by .fernignore)
cli/plant-store/sdk.rs       ← Generated bridge: client() + block_on()
cli/plant-store/main.rs      ← Generated entrypoint (calls custom::register)
plant-store-sdk/             ← Co-generated typed SDK crate
plant-store-types/           ← Co-generated typed model crate

Adding a Custom Command

1. Edit cli/plant-store/custom.rs

This file is protected by .fernignorefern generate will never overwrite it. Register commands in the register() function:

use plant_store_sdk::api::*;

pub fn register(app: CliApp) -> CliApp {
    let app = app.command(
        clap::Command::new("get")
            .about("Get a plant by ID")
            .arg(clap::Arg::new("plantId").required(true))
        ,
        |matches, ctx| {
            let plant_id = matches.get_one::<String>("plantId").unwrap();
            let client = super::sdk::client(ctx);
            let result = super::sdk::block_on(
                client.plants.get(plant_id),
            )?;
            println!("{}", serde_json::to_string_pretty(&result).unwrap());
            Ok(())
        },
    );
    app
}

Then build and test:

cargo build
plant-store get <plantId>

2. Available SDK Clients

The super::sdk::client(ctx) call returns a plant_store_sdk::api::Client with the following sub-clients:

FieldTypeDescription
client.identityplant_store_sdk::api::IdentityClientidentity operations
client.plantsplant_store_sdk::api::PlantsClientplants operations

3. Key Patterns

Get the SDK client (execution-sharing, fully authenticated):

let client = super::sdk::client(ctx);

Run an async SDK call from a sync handler:

let result = super::sdk::block_on(
    client.some_resource.some_method(args),
)?;

Use typed models for request/response serialization:

use plant_store_sdk::api::*;

4. Authentication

Custom commands automatically inherit the CLI's authentication. The following auth schemes are configured:

  • CustomAuth (oauth-client-credentials): env PLANT_STORE_CLIENT_ID, PLANT_STORE_CLIENT_SECRET

No manual auth wiring is needed in custom command handlers.

Regeneration Safety

FileRegenerated?Notes
cli/plant-store/custom.rsNoProtected by .fernignore
cli/plant-store/sdk.rsYesBridges AppContext → SDK client
cli/plant-store/main.rsYesCalls custom::register(app)
plant-store-sdk/YesCo-generated typed SDK crate
plant-store-types/YesCo-generated typed models

After running fern generate, your custom.rs is preserved. All generated code (SDK, types, glue, main.rs) is updated to match the latest API spec. If the SDK surface changes (renamed methods, new sub-clients), update your custom.rs to match.

Build & Test

# Build the CLI (includes custom commands)
cargo build

# Run your custom command
plant-store <your-command> [args]

# Run with verbose output for debugging
RUST_LOG=debug plant-store <your-command> [args]
Repository
fern-api/fern
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.