Skip to content
Back to search

sgsa_scf_ai_wrks_20_nov_2026_public

Tutorial notes on Claude Code skills, hooks and a markdown-based project file system

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lucas-schwengber--sgsa-scf-ai-wrks-20-nov-2026-public/badge.svg)](/listings/lucas-schwengber--sgsa-scf-ai-wrks-20-nov-2026-public)

HTML

<a href="/listings/lucas-schwengber--sgsa-scf-ai-wrks-20-nov-2026-public"><img src="/api/listings/lucas-schwengber--sgsa-scf-ai-wrks-20-nov-2026-public/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 51 lines
  1. ---
  2. title: SGSA/SCF AI workshop 11-20-2026
  3. created: 2026-11-19
  4. updated: 2026-11-19
  5. authors: Lucas da Rocha Schwengber (L), CLAUDE (C)
  6. ---
  7. This repo contain the materials for the tutorial and discussion of the SGSA/SCF AI workshop on 11-20-2026.
  8. ## Tutorial files (L)
  9. `tutorial/` contains the discussion and the brief recap of skills and hooks.
  10. ## Instructions + repo after run (L)
  11. `notes/threads/benchmark_gt/instructions.md` contains a short note providing instructions for the model to execute. Switch to the `after_run` branch to see what the outputs look like.
  12. ## Repository structure (L+C)
  13. | Directory | Contents |
  14. |---|---|
  15. | `src/` | All code, split into the subdirectories below.
  16. | `src/global/` | Reusable code. Nothing in it refers to a specific study. May include packages and general utility scripts.
  17. | `src/experiments/` | Code for specific studies/tasks.
  18. | `src/tests/` | Unit tests for code.
  19. | `data/` | Raw inputs data from diverse sources.
  20. | `outputs/` | Everything the code produces, split into the subdirectories below.
  21. | `outputs/runs/` | Heavy run artifacts (raw arrays, checkpoints, logs), one directory per run.
  22. | `outputs/summaries/` | Light, final products (summary tables, figures).
  23. | `notes/` | Plans, reports and other notes, organized by threads (see below).
  24. Extras:
  25. | Directory | Contents |
  26. |---|---|
  27. | `overleaf/` | Gitignored directory linked with overleaf git.
  28. `src/experiments/`, `outputs/runs/` and `outputs/summaries/` should save files with a structure mirroring the structure of `notes/threads/` for ease of navigation.
  29. ### Threads
  30. `notes/threads` contains major tasks/topics being pursued in the repo. The overall structure is:
  31. ```
  32. notes/
  33. threads/<thread>/
  34. <sub_thread>/ optional: a piece of work with its own plan.md and report.md
  35. ```
  36. - **Tables and figures:** in `outputs/summaries/<thread>/<sub_thread>/`, not in `notes/`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.