Install
$ agentstack add skill-adit-jain-srm-skill-forge-setup ✓ 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
Overview
One-time configuration that asks your preferences (platforms, domains, GitHub username, discovery style) and generates a config all other skill-forge capabilities use.
Setup skill-forge
Run this ONCE per environment. It configures skill-forge to work the way YOU work.
I'll ask you a few questions, then create a config that all other skill-forge capabilities use.
Questions I'll Ask
- GitHub username — Where should published skills be created?
- What platforms do you use? — Cursor / Claude Code / Codex / Gemini / Windsurf / Other
- What domains interest you most? — Frontend / Backend / DevOps / AI / Security / Data / Other
- How aggressive should discovery be? — Conservative (weekly) / Normal (daily) / Maximum (continuous)
- Publishing preferences — Auto-publish when quality passes? Or always ask first?
- Existing skills to integrate with — Which installed skills should skill-forge know about?
What Gets Created
After answering, I'll generate:
memory/user-config.json
All other skills read this config. Your preferences persist across sessions.
Example Config
{
"github_user": "your-username",
"platforms": ["cursor", "claude-code"],
"domains_of_interest": ["backend", "devops", "ai"],
"discovery_aggression": "normal",
"auto_publish": false,
"installed_skills_to_integrate": ["superpowers/*", "azure-skills/*"],
"quality_bar": "validate_before_ship",
"configured_at": "2026-06-04T03:00:00Z"
}
Why This Matters
Without setup:
- skill-forge doesn't know YOUR GitHub username (can't publish for you)
- Discovery is generic (not tuned to your interests)
- Doesn't know what you already have installed (creates duplicates)
With setup:
- Personalized discovery (your domains, your platforms)
- Publishing goes to YOUR account
- Integrates with YOUR existing skills (no duplication)
- Respects your automation preferences
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Adit-Jain-srm
- Source: Adit-Jain-srm/skill-forge
- License: MIT
- Homepage: https://github.com/Adit-Jain-srm/skill-forge#quick-start
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.