redhat-et / redhat-et/docsclaw

Interactive skill for scaffolding new agent configurations

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
2
Forks
1
Avg merge
6h 9m
Merged PRs (30d)
1

Description

Summary

Create a DocsClaw skill (or CLI wizard) that interactively scaffolds a complete agent config directory by asking questions about the agent's purpose, suggesting existing skills, and generating all necessary files.

Motivation

Setting up a new agent requires creating several files (system-prompt.txt, agent-card.json, agent-config.yaml, skills/) with the right structure and content. An interactive wizard would lower the barrier to creating new agents and ensure consistency.

Proposed workflow

  1. Ask about the agent's purpose and domain (e.g., "document reviewer", "data analyst")
  2. Ask about the target LLM provider and model
  3. Suggest relevant existing skills from a catalog
  4. Ask if additional custom skills are needed
  5. Ask about tool requirements (exec, web_fetch, read_file, etc.)
  6. Generate the complete config directory:
    • system-prompt.txt — tailored to the stated purpose
    • agent-card.json — with name, description, skills metadata
    • agent-config.yaml — with appropriate tools and loop settings
    • skills/ — copies of selected existing skills
  7. Optionally generate ConfigMap YAML via the tooling from #6

Implementation options

  • Claude Code skill — a SKILL.md that guides Claude Code through the scaffolding process
  • Cobra subcommanddocsclaw init --config-dir ./my-agent with interactive prompts
  • Both — the skill for Claude Code users, the subcommand for standalone use

Related

  • #6 — Skill-to-ConfigMap conversion tooling (generated config can be immediately converted)
  • #7 — Specialized Dockerfiles (wizard could suggest appropriate image flavor)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing configuration files—system-prompt.txt, agent-card.json, agent-config.yaml, and skills/—and the tooling from #6. Compare the Claude Code skill and Cobra subcommand options, then define the interaction and generated outputs before implementing. Done means a new agent directory can be scaffolded consistently, with optional ConfigMap YAML generation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.