Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
A skill your agent uses when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE…
MITAuto-check passed
Install Percom Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-workflow .claude/skills/percom-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 "percom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-workflow into .claude/skills/percom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-workflow .agents/skills/percom-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 "percom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-workflow into .agents/skills/percom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-workflow .cursor/skills/percom-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 "percom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-workflow into .cursor/skills/percom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-workflow .gemini/skills/percom-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 "percom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-workflow into .gemini/skills/percom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-workflow .github/skills/percom-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 "percom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-workflow into .github/skills/percom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-workflow .opencode/skills/percom-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 "percom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-workflow into .opencode/skills/percom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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
percom-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 703 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 IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE…
- Planning an IEEE PerCom project timeline from venue fit through paper registration
- SKILL.md covers Milestones, Backward plan from the…, Cycle reality: one shot per… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The September submission
What it does
Percom Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for a human-subjects sensing paper and honest handling of the single-annual-deadline cycle.
Its SKILL.md is about 1.5k 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 IEEE PerCom project timeline from venue fit through paper registration
- The September submission
- The early-rejection gate
- The bounded rebuttal
Example prompts
- “/percom-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
Percom Workflow loads about 1.5k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 703 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). 703 words, ~1,455 tokens.
Download SKILL.mdSave it as
.claude/skills/percom-workflow/SKILL.md (or your agent's skills folder).- name
- percom-workflow
- description
- Use when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for a human-subjects sensing paper and honest handling of the single-annual-deadline cycle.
PerCom Workflow
Use this as the project-management skill for a PerCom submission. Replace every date with the current official timetable and work backwards from the HotCRP registration cutoff — which precedes the paper deadline by about a week. PerCom runs a single annual deadline feeding one review round with a bounded rebuttal and an early-rejection gate; there is no journal-style revision, so plan for the paper to be complete at submission.
PerCom is an IEEE Computer Society conference: it has no standing editor-in-chief and no APC in the open-access sense. Rotating leadership is the per-edition General and TPC (Program) Co-Chairs (PerCom 2027 full roster 待核实 as of 2026-07-09), and the cost model is IEEE registration with at least one author presenting in person.
Milestones
- Venue fit: confirm PerCom over ACM UbiComp/IMWUT, MobiCom, SenSys, or IPSN, and confirm the
paper is ready this cycle (
percom-topic-selection). - Data collection lock: IRB/consent secured, subjects recruited, sensing protocol frozen — the long pole for a human-subjects paper.
- Evidence lock: freeze claims, cross-subject splits, baselines, metrics, limitations, and the dataset contents. Nothing can be added in the rebuttal.
- Registration: submit real title, abstract, authors, topics by the earlier registration deadline (PerCom 2027: 4 Sep 2026).
- Submission: upload the anonymized PDF and the open-data plan (PerCom 2027: 11 Sep 2026 AoE).
- Early-rejection gate: notification (~20 Nov 2026) either early-rejects or invites a rebuttal.
- Rebuttal (if invited): answer explicit reviewer questions from existing evidence, anonymously (~26 Nov 2026).
- Decision: accept/reject (~18 Dec 2026); archive reviews, rebuttal, and every submitted version.
- Acceptance: prepare the IEEE Xplore camera-ready (PDF eXpress, eCopyright, ORCID), deposit the de-identified dataset, register, and present in person.
Backward plan from the submission deadline
| Weeks out (heuristic) | Human-subjects sensing milestone |
|---|---|
| 16+ | IRB/consent approved; recruitment and data collection begun (the long pole) |
| 12 | Data collection complete; labeling protocol run with annotator agreement |
| 10 | Claims fixed; cross-subject (LOSO) splits and baselines chosen |
| 8 | Experiments complete; F1/event-level results with per-subject spread computed |
| 6 | Analysis done; limitations drafted alongside results; dataset de-identified |
| 4 | Full draft in the IEEEtran 9+1 template; artifact assembled and anonymized |
| 3 | Internal mock review by a ubicomp reader ("is this within-subject only?") |
| 2 | Limitations hardened, related-work delta sharpened, 9-page budget met |
| 1 | Double-blind sweep on PDF and dataset link; open-data plan final |
| 0 | Registration by its earlier cutoff, then paper + dataset link on HotCRP |
These offsets are planning heuristics only — anchor every one to the current Important Dates page, never to a previous cycle's calendar. Note the 16-week IRB/collection pole: human-subjects data cannot be rushed in the final month.
Show full SKILL.md (283 more words)Show less
Cycle reality: one shot per year, gated early
PerCom runs one annual research deadline. As of 2026-07-09, PerCom 2026 (Pisa) has concluded, so the live next target is PerCom 2027 (Goa; deadline 11 Sep 2026). Two planning consequences:
- There is no revision cycle. A paper that is not complete — especially one lacking cross-subject evidence — cannot be rescued in the rebuttal; it will likely be early-rejected. Finish the evaluation before submitting.
- Missing the annual deadline costs roughly a year at PerCom; ACM IMWUT has rolling quarterly deadlines and a revise cycle, so a paper that needs another round of experiments may be better routed there than held for a year — factor that into routing rather than idling.
Failure modes by stage
- IRB or recruitment slipping pushes data collection into the final month and forces a within-subject-only evaluation — the classic PerCom early-reject in the making.
- Discovering at week 3 that the split was within-subject is fatal with no time to recollect; design the LOSO split at week 10.
- Leaving the anonymized dataset to the final week is how a testbed name, a re-identifying photo, or an owner string leaks identity under double-blind review.
- Skipping the mock review forfeits the one chance to hear "your evaluation is within-subject" from a friend instead of a reviewer — and there is no revision to fix it.
- Treating the rebuttal as a revision and planning to "add the experiment then" — the process neither expects nor permits it.
Coordination notes
- Assign one owner for IRB/consent and the dataset, and another for the double-blind anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, dataset, and (later) rebuttal — the discussion must quote them precisely and stay anonymous.
Output format
[Current stage] idea / IRB+collection / evidence / writing / registration / submitted / rebuttal / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness -- IRB/collection is usually one>
[Risk register] <IRB / cross-subject evaluation / 9-page budget / anonymity / dataset / presentation>
[Owner map] <task -> person or role>© 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 PerCom-Skills/skills/percom-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Percom 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 |
|---|---|---|---|---|---|---|
| Percom Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 98k | 1 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Performing Timeline Reconstruction With Plasomukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Notes | Apache-2.0 |
Similar skills
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
Building Super Timelines With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Generate forensic super-timelines with Plaso's log2timeline.py, pinfo.py, psort.py, and psteal.py CLI tools (fusing file-system MACB, registry, EVTX, browser history, prefetch, LNK, and more), then…
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 Percom Workflow
What does Percom Workflow do?
A skill your agent uses when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE…. Percom Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for a human-subjects sensing paper and honest handling of the single-annual-deadline cycle.
When should I use Percom Workflow?
Percom Workflow fits situations like: planning an IEEE PerCom project timeline from venue fit through paper registration; the September submission; the early-rejection gate; the bounded rebuttal.
How do I install Percom Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-workflow -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Percom Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-workflow -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-workflow in your project. Codex loads it when a task matches its description.
Can I use Percom 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 percom-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/percom-workflow, .gemini/skills/percom-workflow, .github/skills/percom-workflow and .opencode/skills/percom-workflow in your project.
What does Percom Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Percom Workflow is instructions for the agent only.
Does Percom 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 Percom 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 Percom Workflow use?
Percom 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 Percom Workflow use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 Percom Workflow?
Skills that share tags, products or a category with Percom Workflow: Project Timeline Report (thedotmack/claude-mem, 98k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Generating Forensic Timelines With Hayabusa (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Percom 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.