by display

Other Community v1.0

Skill notes

When to Use This Skill

Use this skill when you are: ✅ Rendering campaign status for /by:status, /by:watch, or phase transitions ✅ Formatting screening reports (liabilities, developability, structure scores) ✅ Showing ranked results for /by:results or any final campaign output ✅ Displaying errors or quota warnings that need user attention

Inputs

This skill is consumed by other skills. Inputs are the data objects to be rendered: Required (one of): Campaign checkpoint object — { campaign_id, target, phases: [{name, status, time, details}, ...], current_phase }. Source: by-campaign-manager (campaign_state.json). Ranked design list — [{ design_id, composite, ipSAE, ipTM, pLDDT, liabilities, verdict }, ...]. Source: by-scoring / by-screening.

Outputs

Markdown strings printed to the terminal. No files written by this skill itself. Output · When · Template ID Campaign status banner · /by:status, phase transitions · banner.campaign-status Progress-during-design line · /by:watch, mid-pipeline · progress.design Ranked results table · /by:results, campaign close · table.ranked-results

Clarification Questions

⚠️ CRITICAL: ASK THIS FIRST — confirm there is something to render before invoking this skill. What are you trying to render? (ASK THIS FIRST) — A campaign status, a ranked results table, a screening report, an error, or a checkpoint? Each maps to a different template. Without this, do not generate any output. Which data object do you have? — Pass the campaign checkpoint, the ranked design list, or the screening report object. The skill cannot make up values; if a field is missing, leave it blank or mark — (em-dash).

Standard Workflow

🚨 MANDATORY: COPY TEMPLATES FROM references/output-format-spec.md VERBATIM — DO NOT IMPROVISE LAYOUT 🚨 Identify the render type. Match the data object to one of the templates above. Load the template from references/output-format-spec.md. Fill the slots with values from the input object. Use — (em-dash) for missing values; never invent numbers. Pick the right status symbol from the table below.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@001TMF · v1.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview by-display.preview
# Ranked Results Table

Use for `/by:results` and final campaign output. ```markdown ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BY ► RESULTS: {campaign_name} — {N} candidates ranked ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ # Design Composite ipSAE ipTM pLDDT Liabilities Verdict ─── ──────────── ────────── ─────── ────── ────── ───────────── ────────── 1 design_003 0.871 0.85 0.82 91.2 0 crit ✓ LAB-READY 2 design_007 0.823 0.80 0.79 88.5 1 warn ✓ LAB-READY 3 design_001 0.756 0.72 0.75 85.1 0 crit ◆ FOLLOW-UP 4 design_012 0.534 0.45 0.62 78.3 2 crit ✗ NOT VIABLE

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.