cellm-feedback

Document upstream CELLM findings as structured Markdown evidence.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/murillodutt/cellm --skill cellm-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cellm-feedback
Source: https://github.com/murillodutt/cellm/tree/main/cellm/skills/cellm-feedback
Command: npx skills add https://github.com/murillodutt/cellm --skill cellm-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates standardized, upstream feedback for CELLM engineering by emitting evidence-first Markdown documents that capture bugs, anti-patterns, deprecation gaps, and harness surprises in a consistent format.

Core Features & Use Cases

  • Produce docs under docs/evidence with a date-stamped slug for each finding.
  • Optionally register reusable atoms to enable cross-project reuse and knowledge sharing.
  • Enforce a fixed template (data, executive summary, impact, proposals, acceptance criteria) to streamline triage and governance.

Quick Start

Invoke with /cellm:cellm-feedback <slug> to generate a structured evidence MD and optional atom registrations.

Frequently Asked Questions about cellm-feedback

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

FAQPage Schema
How do I document upstream CELLM bugs and harness surprises as structured evidence?▼

You document upstream CELLM bugs by generating evidence-first Markdown files using a fixed template that captures data, executive summary, impact, proposals, and acceptance criteria to streamline triage and governance.

What is the best way to standardize feedback for CELLM engineering teams?▼

Standardizing CELLM feedback requires enforcing a fixed template with frontmatter metadata and date-stamped slugs under a docs/evidence path, ensuring consistent capture of bugs, anti-patterns, and deprecations.

How do I register reusable atoms for cross-project CELLM findings?▼

You register reusable atoms during the evidence generation process to enable cross-project knowledge sharing and reuse of documented findings like anti-patterns and harness surprises across CELLM skills and MCP tooling.

Can I use a fixed template to generate Markdown feedback for MCP tooling deprecations?▼

Yes, you can generate Markdown feedback for MCP tooling deprecations by enforcing a fixed template that includes frontmatter metadata, executive summaries, impact assessments, proposals, and acceptance criteria.

What is included in the fixed template for structured upstream feedback?▼

The fixed template includes data, an executive summary, impact analysis, proposals, and acceptance criteria, supplemented by frontmatter metadata and a date-stamped slug for each finding.

Does generating evidence-first Markdown for CELLM skills require external dependencies?▼

No, generating evidence-first Markdown for CELLM skills requires no external dependencies, operating independently to produce structured documentation and optional atom registrations for reusable findings.