원클릭으로 Manus에서 모든 스킬 실행

syncing-icorsi-copies

스타1

포크0

업데이트2026년 7월 3일 08:29

Use this skill when checking whether the manual copies of the icorsi-notes claude-home agents and skill have drifted from their dotfiles-private source, or re-syncing them after an edit. Triggers include 'sync the icorsi copies', 'check icorsi drift', 'did the icorsi agents drift', 're-sync claude-home', 'I edited the school agents', or any edit to the school cs-material-researcher/cs-notes-auditor/cs-notes-author/cs-notes-formatter agents or the authoring-course-notes skill in ~/dotfiles-private/claude/. Does NOT cover editing the agents or skill content itself (edit in dotfiles-private, then invoke this skill to propagate) and does NOT cover icorsi-notes/claude-home/CLAUDE.md, which is not a copy and is edited in place.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nicolkrit999

nicolkrit999/portainer-templates

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Syncing icorsi copies

icorsi-notes/claude-home/ in this repo holds manual copies of 4 agents (cs-material-researcher.md, cs-notes-auditor.md, cs-notes-author.md, cs-notes-formatter.md, sourced from ~/dotfiles-private/claude/school/.claude/agents/) and one skill directory (skills/authoring-course-notes/, sourced from ~/dotfiles-private/claude/parked/authoring-course-notes/).

The authoritative command list - both the diff commands and the re-copy commands - lives in icorsi-notes/claude-home/README.md. Always read that README before acting; do not hardcode or duplicate its commands here, since it may be updated independently of this skill.

This is a mechanical, single-agent procedure - no agent loop is needed.

Procedure

Read icorsi-notes/claude-home/README.md and run the drift-check diffs it documents (the 4 agent file diffs plus the diff -r on authoring-course-notes/).
If every diff is empty: report "in sync" and stop.
If any diff shows drift, determine direction before touching anything:
- Source of truth is always ~/dotfiles-private/claude/.... If the drift is because the source changed and the copy is stale, re-copy source → copy using the exact commands from the README.
- If the copy has changes the source lacks (someone edited claude-home directly, which the README forbids), STOP and ask the user before overwriting anything. Never silently discard those edits - they may need to be ported back into dotfiles-private first.
After re-copying, re-run the same drift-check diffs to confirm every one is now empty. Report exactly which files were re-synced (by path), or confirm nothing needed re-syncing.

Exit condition

All diffs listed in the README (4 agent files + the authoring-course-notes directory diff) come back empty.

Out of scope

Editing agent or skill content: make the change in ~/dotfiles-private/claude/... first, then invoke this skill to propagate it - this skill only copies, it does not author content.
icorsi-notes/claude-home/CLAUDE.md: this is the daemon's own constraints file, not a copy of anything, and is edited in place - never diffed or re-synced.

이 저장소의 다른 Skills

같은 저장소

authoring-course-notes

nicolkrit999/portainer-templates

Use this skill when creating detailed study notes or course documentation from source material and (optionally) compiling them to PDF - for any CS or math course (linear algebra, calculus, discrete math, statistics, programming). Triggers: 'make notes for this chapter', 'write detailed notes on …', 'turn this course material into a PDF', 'create documentation explaining every topic in …', 'compile these notes to PDF', 'typst/latex notes for …'. Works from ANY course folder (callable by name without an absolute path). Orchestrates reading the source → authoring the explanations → formatting/compiling through the project's `cs-notes` Nix dev environment (Typst, LaTeX via Tectonic, Pandoc, diagrams, plotting, Python). Use whenever study notes / documentation should be produced as a polished file, especially when LaTeX/Typst/PDF compilation is involved. NOT for a page-capped exam cheat sheet (maximal density fitted to a hard page limit) - that's creating-exam-cheat-sheets.

2026-07-031

adding-compose-services

nicolkrit999/portainer-templates

Use this skill when the user wants to bring a brand-new service into this Portainer homelab repo. Trigger phrases include 'add <service> to my homelab', 'set up <service> behind the tunnel', 'create a compose for <service>', 'deploy <service>', 'I want to self-host <service>'. It researches the service, has docker-compose-architect create the new `<service>/docker-compose.yml` per repo rules, runs compose-security-auditor and compose-consistency-linter in parallel, loops fixes back through docker-compose-architect, and hands off the Cloudflare Tunnel target plus the full list of `${VAR}`s to set in Portainer. It does NOT cover auditing or linting services that already exist across the repo (use auditing-compose-repo for that) and it does NOT cover editing an already-deployed service's compose file (dispatch docker-compose-architect directly for that).

2026-07-031

auditing-compose-repo

nicolkrit999/portainer-templates

Use this skill when the user wants a repo-wide check across services that already exist in this Portainer homelab repo. Trigger phrases include 'audit my composes', 'security check the repo', 'are my composes consistent', 'sweep all services', 'check the whole repo for violations'. It runs compose-security-auditor and compose-consistency-linter across all ~70 service directories in parallel, triages the combined findings by severity with the user, dispatches docker-compose-architect to apply exact fixes, and re-runs only the affected reviewer(s) on the changed services. It does NOT cover onboarding a brand-new service (use adding-compose-services for that, which includes its own scoped review loop) and it does NOT edit files itself - all fixes are applied by docker-compose-architect.

2026-07-031

migrating-portainer-stacks

nicolkrit999/portainer-templates

Use this skill when bringing a stack that is currently only running in Portainer under git management in this repo, extracting its live configuration, and templating it per repo conventions. Triggers include 'migrate <stack> to git', 'extract this stack from Portainer', 'bring <service> under git management', 'import the running stack', 'convert my Portainer stack to a template'. Does NOT cover brand-new services that have never been deployed (use adding-compose-services) and does NOT cover repo-wide audits of already-migrated stacks (use auditing-compose-repo).

2026-07-031

name

syncing-icorsi-copies

description

Syncing icorsi copies

This is a mechanical, single-agent procedure - no agent loop is needed.

Procedure

Read icorsi-notes/claude-home/README.md and run the drift-check diffs it documents (the 4 agent file diffs plus the diff -r on authoring-course-notes/).
If every diff is empty: report "in sync" and stop.
If any diff shows drift, determine direction before touching anything:
- Source of truth is always ~/dotfiles-private/claude/.... If the drift is because the source changed and the copy is stale, re-copy source → copy using the exact commands from the README.
- If the copy has changes the source lacks (someone edited claude-home directly, which the README forbids), STOP and ask the user before overwriting anything. Never silently discard those edits - they may need to be ported back into dotfiles-private first.
After re-copying, re-run the same drift-check diffs to confirm every one is now empty. Report exactly which files were re-synced (by path), or confirm nothing needed re-syncing.

Exit condition

All diffs listed in the README (4 agent files + the authoring-course-notes directory diff) come back empty.

Out of scope

Editing agent or skill content: make the change in ~/dotfiles-private/claude/... first, then invoke this skill to propagate it - this skill only copies, it does not author content.
icorsi-notes/claude-home/CLAUDE.md: this is the daemon's own constraints file, not a copy of anything, and is edited in place - never diffed or re-synced.