Credit Cycle Analysis
sickn33/agentic-awesome-skills
Debtor and creditor credit-cycle analysis: weighted collection or payment days, ageing buckets, credit limit utilisation and gap against benchmark.
A skill your agent uses when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the…
MITAuto-check passed
Install Chi Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/CHI-Skills/skills/chi-workflow .claude/skills/chi-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "chi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflow into .claude/skills/chi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/CHI-Skills/skills/chi-workflow .agents/skills/chi-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflow into .agents/skills/chi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/CHI-Skills/skills/chi-workflow .cursor/skills/chi-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflow into .cursor/skills/chi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path CHI-Skills/skills/chi-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/CHI-Skills/skills/chi-workflow .gemini/skills/chi-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflow into .gemini/skills/chi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/CHI-Skills/skills/chi-workflow .github/skills/chi-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflow into .github/skills/chi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/CHI-Skills/skills/chi-workflow .opencode/skills/chi-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-workflow into .opencode/skills/chi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chi-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 620 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the…
- Planning an ACM CHI submission cycle end to end — the single September deadline
- SKILL.md covers The CHI 2027 calendar, Working backwards from…, Pre-positioning for the… and The post-acceptance chain is…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Two-round review with a five-week revise-and-resubmit window
What it does
Chi Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an ACM CHI submission cycle end to end — the single September deadline
- Two-round review with a five-week revise-and-resubmit window
- December decisions
- The TAPS and publication-ready chain
Example prompts
- “/chi-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chi Workflow loads about 1.4k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 620 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 620 words, ~1,421 tokens.
Download SKILL.mdSave it as
.claude/skills/chi-workflow/SKILL.md (or your agent's skills folder).- name
- chi-workflow
- description
- Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.
CHI Workflow
CHI is a one-shot annual venue with a two-round review inside the cycle. The dates
below are the CHI 2027 calendar as posted on chi2027.acm.org and read on 2026-07-08
via search renderings (the site refuses direct automated fetches); treat them as this
cycle's plan and reverify on the live page at each stage.
The CHI 2027 calendar
| Date | Stage | Who must act |
|---|---|---|
| 2026-07-30 | PCS submission site opens | Submitting author sets up the record early |
| 2026-09-10 (Thu) | Full papers due — including videos and supplementary | Everyone; no separate abstract deadline was posted |
| ~late Oct / early Nov 2026 (待核实) | Round-1 outcome: revise-and-resubmit invitation or reject | 1AC/2AC verdict arrives; clear your calendar if invited |
| 2026-12-03 | Revised paper + author response due (≈5 weeks after round-1) | Whole author team, on a fixed clock |
| 2026-12-17 | Final notification after round 2 / PC meeting | — |
| 2027-01-14 | Camera-ready source due in ACM TAPS | Paper lead + whoever owns LaTeX/Word source |
| 2027-02-18 | Publication-ready deadline on PCS (final materials, supplemental, optional video preview) | Paper lead |
| 2027-03-04 | Registration deadline + video presentation deadline | Presenting author + grant admin |
| 2027-05-10 – 05-14 | CHI 2027, Pittsburgh, Pennsylvania, USA | Presenter |
Two structural facts drive all planning: everything is due on September 10 — CHI gives no later supplement or video slot — and the December 3 revision window is only five weeks long, landing across November holidays for much of the community.
Working backwards from September 10
- T−16 weeks (mid-May): study data collection finished. A CHI paper whose study is still running in July will submit an under-analyzed paper.
- T−10 weeks: analysis locked; contribution type and subcommittee choices drafted
(
chi-topic-selection); skeleton of the paper written. - T−6 weeks: full draft exists; video figure storyboarded. Video production, captioning, and consent checks for footage reliably take three weeks.
- T−3 weeks: internal "mock 1AC" read by someone outside the project; fix the contribution statement before polishing prose.
- T−1 week: run the
chi-submissionaudit; upload a complete package to PCS and re-download it. PCS accepts revisions until the deadline, so upload early and overwrite.
Pre-positioning for the five-week revision
The revise-and-resubmit window cannot be extended, so buy time before it opens:
Before round-1 results arrive (October):
[ ] Keep the study environment alive — do not archive the analysis pipeline,
delete participant contact channels, or let IRB approval lapse; a small
follow-up analysis is the most common revision request you can predict.
[ ] Pre-agree author availability for the five weeks around Nov-Dec.
[ ] Set up the tracked-changes toolchain now (latexdiff or Word tracking)
so day 1 of the window is spent revising, not configuring.
[ ] Draft the response-letter template with one section per reviewer.If invited, treat it as a real second round, not a formality: at CHI as much as half
of revised papers can still be rejected at the PC meeting (the posted process warns up
to 50%; at CHI 2026, 65.5% of resubmissions were accepted). See chi-author-response.
Show full SKILL.md (229 more words)Show less
The post-acceptance chain is longer than at most venues
Acceptance in December starts a four-deadline pipeline — TAPS source (January),
publication-ready PCS package with accessibility metadata (February), registration and
the presentation video (March), then the conference (May). Each has a different owner
and a different failure mode; assign names in December, not February. Details in
chi-camera-ready.
Risk register for the cycle
| Risk | Window | Mitigation |
|---|---|---|
| Study slips past May | Spring | Cut scope to a short paper rather than submit thin data |
| Video figure unfinished at deadline | September | Storyboard at T−6 weeks; captions are mandatory work, not polish |
| Round-1 invite lands during travel/holidays | Oct–Dec | Availability pact signed in October |
| Requested analysis impossible (data deleted, IRB lapsed) | Nov | Keep the pipeline warm until December 17 |
| TAPS rejects source formatting | January | Compile on the ACM class early; do not hand-hack the PDF |
| Missing alt text blocks publication-ready sign-off | February | Write figure descriptions during drafting, not after acceptance |
| Nobody registered by March 4 | March | Registration owner named at acceptance |
If the December answer is no
Rejected CHI papers have a well-worn afterlife: the reviews map cleanly onto CSCW
(different deadline rhythm), DIS, IUI, or a TOCHI journal submission where length
limits will not pinch. Do the re-route triage within two weeks of the decision while
the reviews are fresh — see the venue table in chi-topic-selection — and log which
criticisms were CHI-specific versus substantive.
Output format
[Cycle] CHI 2027 (papers due 2026-09-10; verified 2026-07-08, reverify live)
[Today → next gate] <stage name, days remaining>
[Stage owners] submission: <name> / revision: <name> / TAPS: <name> / registration: <name>
[Top calendar risk] <risk + mitigation from the register>
[Fallback venue] <where this goes if December says no>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in CHI-Skills/skills/chi-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Chi Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chi Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Credit Cycle Analysissickn33/agentic-awesome-skills | 47k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Acm Chi Conference On Human Factors In Computing Systemsfranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Dengxiaofeng Cycle Industryquestflowai/investorskills | 1.9k | — | ~475 | Automated safety check: Pass | MIT | |
| Review Cyclecatlog22/Claude-Code-Workflow | 2.1k | — | ~148 | Automated safety check: Pass | MIT | |
| PR Cyclejaemk/cached | 2.1k | — | ~4.8k | Automated safety check: Notes | MIT |
Similar skills
Acm Chi Conference On Human Factors In Computing Systems
franklee16/academic-research-skills
A skill your agent uses when targeting ACM CHI Conference on Human Factors in Computing Systems (CHI) or deciding whether a computer-science manuscript fits this venue.
Dengxiaofeng Cycle Industry
questflowai/investorskills
A skill your agent uses when evaluating stocks through Deng Xiaofeng's cycle-and-industry lens: deep industry research, cycle position awareness, supply-demand dynamics, and buying leaders at cycle…
Review Cycle
catlog22/Claude-Code-Workflow
Chain-loaded review cycle. An agent skill from catlog22/Claude-Code-Workflow.
PR Cycle
jaemk/cached
PR review-and-update cycle — the orchestrator that takes a PR from review to resolved.
Marks Cycles
questflowai/investorskills
A skill your agent uses when evaluating markets through Howard Marks-style second-level thinking, credit cycles, risk premiums, market psychology, and defensive versus aggressive posture.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Chi Workflow
What does Chi Workflow do?
A skill your agent uses when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the…. Chi Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.
When should I use Chi Workflow?
Chi Workflow fits situations like: planning an ACM CHI submission cycle end to end — the single September deadline; two-round review with a five-week revise-and-resubmit window; december decisions; the TAPS and publication-ready chain.
How do I install Chi Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a claude-code`. Or copy the skill folder (CHI-Skills/skills/chi-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/chi-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Chi Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a codex`. Or copy the skill folder (CHI-Skills/skills/chi-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/chi-workflow in your project. Codex loads it when a task matches its description.
Can I use Chi Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chi-workflow, .gemini/skills/chi-workflow, .github/skills/chi-workflow and .opencode/skills/chi-workflow in your project.
What does Chi Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Chi Workflow is instructions for the agent only.
Does Chi Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Chi Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Chi Workflow use?
Chi Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Chi Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Chi Workflow?
Skills that share tags, products or a category with Chi Workflow: Credit Cycle Analysis (sickn33/agentic-awesome-skills, 47k stars), Acm Chi Conference On Human Factors In Computing Systems (franklee16/academic-research-skills, 223 stars), Dengxiaofeng Cycle Industry (questflowai/investorskills, 1.9k stars) and Review Cycle (catlog22/Claude-Code-Workflow, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chi Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.