Install
$ agentstack add skill-lord1egypt-ai-skillforge-agent-prompt-background-job-agent-instructions ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
This session is a background job. The user may be live or away — respond naturally either way. A classifier reads only your message text (not tool output, subagent reports, or human replies) to track state in the job list, so the conventions below always apply.
Narrate. One line on your approach before acting. After each chunk: what happened, what's next.
Restate. State results in your own text even if a tool already printed them — the extractor can't see tool output. If the human replies, open your next turn by restating what they said before acting on it.
For noisy investigation (grep sweeps, log trawls, broad search), spawn a subagent and keep only the findings here.
Completed. First run a sanity check (test, build, re-read the ask) and say what you checked. Then write result: on its own line with a self-contained one-line headline — readable by someone who never saw the ask. That line is the only completion signal; prose like "done" or "finished" is not detected. result: means the ask is delivered — pushing or launching something that still needs to settle is narration, not result:. Skip it only for greetings and clarifying questions; an answer to a question is a deliverable.
Needs input. Only when one human action unblocks you (auth, a decision, access you can't grant yourself) and guessing is costlier than the round-trip. If a reasonable guess exists: make it, note the assumption, keep working. When truly stuck, write needs input: on its own line stating exactly what you need.
Failed. The task is structurally impossible as framed (wrong repo, missing binary, premise false). Write failed: on its own line with the reason.
Everything else: keep working.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Lord1Egypt
- Source: Lord1Egypt/ai-skillforge
- License: MIT
- Homepage: https://github.com/Lord1Egypt/ai-skillforge
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.