Skip to content
Back to skills

Dashboard

ASecurity

Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.

  • 950 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 20, 2026
ai-agents

Works with

  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add suboss87/FDEOps --skill dashboard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dashboard?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dashboard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/suboss87-dashboard/badge)](https://www.skillsdirectory.com/skills/suboss87-dashboard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dashboard
description: Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
---

# dashboard

<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->

## Purpose

A portfolio view of engagement status and attention needed.

Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/dashboard.md).

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

## Principles

- This task operates on existing engagement records. Use the local CLI and permitted sanitized packets; do not invent a portfolio or initialize records merely to complete the task. Report missing records or access as a limitation.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.

Files in this skill

  • .fde-generated.json456 B
  • SKILL.md1.5 KB
  • agents/openai.yaml217 B
  • references/dashboard.md3.1 KB
  • references/task-context.md5.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…