ghe-status
Check GitHub Elements Workflow Status
Teams need a quick view of GitHub Elements workflow health without changing issue state. This skill produces a read-only status overview for active threads, phases, and warnings.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ghe-status" from https://skillstore.io/skills/emasoft-ghe-status.md and its manifest at https://skillstore.io/api/skills/emasoft-ghe-status/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ghe-status". Show the current GitHub Elements status.
Expected outcome:
The response summarizes active threads, phase counts, available work, and workflow health indicators in a compact status report.
Using "ghe-status". What work is ready but not claimed?
Expected outcome:
The response lists ready issues that are not assigned, with enough context to choose the next action.
Using "ghe-status". Give me a health check for the workflow.
Expected outcome:
The response calls out violations, checkpoint frequency, and recent completions so the team can spot coordination issues.
Security Audit
High RiskMost external command findings are false positives caused by Markdown inline code and fenced output examples. The hidden home directory access is confirmed because a read-only status skill grants write scope to ~/.claude. Semantic review also found absolute behavioral override language and mandatory report posting that conflict with read-only expectations.
Confirmed security concerns (3)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (7)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/emasoft-ghe-status/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/emasoft-ghe-status?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/emasoft-ghe-status?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emasoft-ghe-status/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/emasoft-ghe-status.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Emasoft. (2026). ghe-status security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emasoft-ghe-status/audits/8BibTeX citation
@techreport{emasoft-emasoft-ghe-status-2026,
author = {Emasoft},
title = {ghe-status security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/emasoft-ghe-status/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ghe-status security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Emasoft"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/emasoft-ghe-status/audits/8"
identifiers:
- type: other
value: "skillstore:emasoft-ghe-status:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Start a Coordination Session
Get a quick overview of active work before assigning or reviewing GitHub Elements issues.
Check Review Load
See how many items are in DEV, TEST, and REVIEW before planning the next handoff.
Find Ready Work
Identify ready issues that are not claimed without changing the workflow state.
Try These Prompts
Show the current GitHub Elements status overview.
Show active GitHub Elements threads and summarize the DEV, TEST, and REVIEW phase counts.
Check GitHub Elements status and highlight ready work that is not claimed.
Run a GitHub Elements status overview with active threads, phase distribution, recent completions, and workflow health warnings.
Best Practices
- Use this skill at session start before claiming or transitioning issues.
- Keep local settings current so disabled or reduced output is intentional.
- Use ghe-report when you need detailed metrics or epic-specific analysis.
Avoid
- Do not use this skill to claim issues or change issue phases.
- Do not treat the status overview as a full audit or detailed report.
- Do not post status information externally unless the user explicitly requests it.