nicsuzor/project
aops-core/skills/project/SKILL.md
Scaffold research project repositories with smart defaults — repo creation, directory structure, CI/CD, documentation, and PKB integration in one pass.
$ install --global
skillsauthnpx skillsauth add nicsuzor/academicops projectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 8, 2026, 7:08 AM294.0s3 files scanned
SKILL.md
- name:
- project
- type:
- skill
- category:
- instruction
- description:
- >
- modifies_files:
- true
- needs_task:
- false
- mode:
- conversational
Project Scaffolding Guidelines
Initialize and configure research project repositories with complete operational infrastructure.
Core Directives
- Information Gathering: Learn the project title, research type (empirical, qualitative, library, mixed), collaboration team scope, data pipeline choice (dbt, DuckDB, MLflow, DVC), and publication formats. Propose sensible defaults before execution.
- Infrastructure Rules:
- Establish git hygiene (add appropriate
.gitignoreand configure pre-commit hooks). - Ensure raw research data directories (
data/raw/) are configured as immutable. - Create documentation stubs and issue templates.
- Establish git hygiene (add appropriate
- Execution: Follow the setup procedure in
instructions/initto construct the repository.
Exclusions
- Do not add tools or directories unless explicitly selected by the user.
- Do not configure secrets or credentials (provide instructions instead).
- Do not create task logs, milestones, or epics (delegate to
/planner).
Output Expectations
- Present the proposed repository structure and tooling selection concisely to the user.
- Once approved, execute, report successful initialization, and list next-step commands.
Related Skills
nicsuzor/end_session
data-ai
VerifiedTrustedCommunity
Canonical session close — commit, push, PR, release_task, reflection blocks, handover. Use /dump for emergency bail (no commit/PR/reflection).
2SKILL.mdUpdated Jul 7, 2026
nicsuzor/dump
data-ai
VerifiedTrustedCommunity
Emergency session bail — fast resume task + short handover, no commit/PR/reflection. For when you (or the user) need a clean context now. Use /end-session for canonical close.
2SKILL.mdUpdated Jul 7, 2026
nicsuzor/daily
data-ai
VerifiedTrustedCommunity
Daily note lifecycle — compose and maintain a factual daily note. Reports the state of the day; does not prioritise or recommend. SSoT for daily note structure.
2SKILL.mdUpdated Jul 7, 2026
nicsuzor/narrative-digest
testing
VerifiedTrustedCommunity
Launder supervisor/worker task-log output into a Nic-facing narrative — what happened, where things are headed, and what (if anything) is genuinely his to decide. Never relays raw process detail (worker IDs, thread pointers, log paths) or verbatim task-log stream-of-consciousness.
2SKILL.mdUpdated Jul 7, 2026