القائمة
Add a new authoritative source agency to data/sources/agencies.json so that future cert evaluations can cite it.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a new security certification to the roadmap by writing data/certs/<vendor>/<slug>.json from official + third-party sources.
Compute every cert's tier (foundational / associate / professional / expert / specialty) by simulating three independent reviewer personas, and gate the run on persona disagreement.
Curate cross-vendor "commonly taken before" recommendations based on community / industry reputation. Adds entries to prerequisites.recommended_certs[] tagged with source "community" and a one-sentence rationale. Distinct from infer-relationships (which only handles official ladders).
Propose prerequisite cert relationships across the entire roadmap from neutral AI analysis of cert facts. Both within-vendor ladders and cross-vendor industry-conventional flows are in scope.
Triage a GitHub Issue (add-cert / update-cert / add-source / evaluation) and dispatch to the right skill, ending with a draft PR or a clarifying comment.
Bootstrap-time skill that web-researches the latest popular security certifications per domain and drafts JSON stubs for any missing ones, as one PR per domain.
| name | add-source |
| description | Add a new authoritative source agency to data/sources/agencies.json so that future cert evaluations can cite it. |
An add-source-agency Issue arrives proposing a new authoritative source
agency (governmental body, ISO/IEC 17024 accreditor, recognised non-profit
standards body).
third_party_evaluations[].url on individual certs.kebab-case, jurisdiction-prefixed when the same
acronym exists in multiple jurisdictions (e.g. ncsc-uk, ncsc-nl).data/sources/agencies.json preserving the existing
field order: id, name, jurisdiction, url, trust_tier, use.
Keep the array alphabetically by id within trust_tier groups for
stable diffs.make validate (the JSON Schema covers the cert
files; agencies.json is hand-curated, so do a jq . data/sources/agencies.json
to confirm valid JSON at minimum).high - direct governmental / standards-body authority.medium - recognised industry consortium with transparent governance.vendor - certification issuers themselves; only valid as the source-of-truth for that vendor's own certs.