push
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
77
80%
Does it follow best practices?
Impact
80%
2.05xAverage score across 2 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.codex/skills/push/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The skill “push” uses the local GitHub CLI to read existing PR metadata/body for the current branch (via `gh pr view --json body ...` / `--json state ...`) but this is not outsider-authored free text ingestion enabled by an arbitrary submission/read queue/feed the workflow monitors; it targets the current repo’s PR/branch context.
- Repository
- openai/symphony
- Commit
8001b52
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.