academic-research-comp…
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing,…
Creates a GitHub repository for the website project, initializes git, and pushes the code.
$ npx -y skills add GRCEngClub/claude-grc-engineering --skill website-repo --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/website-repoContext preview
The summary Claude sees to decide when to auto-load this skill.
Creates a GitHub repository for the website project, initializes git, and pushes the code.
name: website-repo description: Creates a GitHub repository for the website project, initializes git, and pushes the code. allowed-tools: Bash, Read, Write, Edit, Glob
You are running the `/grc-portfolio:repo` skill. Your job is to create a GitHub repository for the website project and push the code.
Find `site-config.json`:
Read it and validate that `status.buildComplete === true`. If not, tell the user to run `/grc-portfolio:build` first.
Check that `gh` CLI is installed and authenticated:
gh --version gh auth status
If not installed, tell the user to run:
brew install gh gh auth login
Ask the user:
Check if `.gitignore` exists in the project directory. If not, create one:
# Dependencies node_modules/ # Build output dist/ # Environment variables .env .env.local .env.production # OS files .DS_Store Thumbs.db # IDE .vscode/ .idea/ # Logs *.log npm-debug.log* # Lambda packages lambda/*.zip
If it exists, verify it includes at least `node_modules`, `dist`, `.env`, `.env.local`, and `.DS_Store`. **If any of those entries are missing, add them before staging any files** — `git add -A` will happily stage `.env.local` with secrets in it otherwise.
cd <projectDir> git init
Before staging, confirm `.env*` files are ignored:
git check-ignore -q .env .env.local 2>/dev/null && echo "ok: env files ignored"
If that fails (exit code 1), stop and fix `.gitignore` — do not run `git add -A` until env files are ignored.
git add -A # Sanity check: nothing under .env* should be staged. if git diff --cached --name-only | grep -E '^\.env(\.|$)'; then echo "ERROR: env file staged — unstage it and fix .gitignore" >&2 exit 1 fi git commit -m "Initial commit: scaffolded GRC portfolio website"
gh repo create <repoName> --<visibility> --source . --push
This creates the repo on GitHub, sets the remote, and pushes the code.
Get the repo URL and owner:
gh repo view --json url,owner
Update `site-config.json`:
Tell the user:
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing,…
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
Use when interpreting AWS Secrets Manager connector output, deciding between inspector and retrieve modes, drafting SCF-mapped controls for rotation / KMS /…
Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
Interpret CrowdStrike Falcon findings for sensor coverage, policy visibility, and host group scoping.
Interpret datadog-inspector findings and translate Datadog monitoring, audit, log-retention, SSO, and RBAC results into GRC evidence and remediation.