Individual skill
ralph-specum-feedback
This skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.
plugins/ralph-specum-codex/skills/ralph-specum-feedback/SKILL.md
Source commit ac7251a0a056b51435192443775f3cbbc4675cba
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 567
- Repository last updated
- Oct 28, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-coding Repository topic
- ai Repository topic
- ai-agents Repository topic
- autonomous-coding Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- coding-agent Repository topic
- developer-tools Repository topic
- llm Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 927 bytesagents/openai.yamlasset · 241 bytes
Read excerpt
# Ralph Specum Feedback
Use this to capture product feedback or bug reports for Ralph Specum.
## Action
1. Summarize the issue, request, or missing behavior.
2. Gather the minimum reproducible context, affected files, commands, environment details, and whether the issue is on the Codex package or Claude plugin surface.
3. If `gh` is available and the user wants submission, create a GitHub issue.
4. If `gh` is unavailable or the user only wants a draft, produce a ready-to-paste issue body and the repository issue URL.
## Output
Keep the report concrete. Include expected behavior, actual behavior, reproduction steps, and any relevant state files or logs.