Longbridge Research
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
A skill your agent uses when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and…
Install Sensys Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-workflow .claude/skills/sensys-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 "sensys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-workflow into .claude/skills/sensys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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/SenSys-Skills/skills/sensys-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 sensys-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-workflow .agents/skills/sensys-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 "sensys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-workflow into .agents/skills/sensys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-workflow .cursor/skills/sensys-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 "sensys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-workflow into .cursor/skills/sensys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 SenSys-Skills/skills/sensys-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 sensys-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-workflow .gemini/skills/sensys-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 "sensys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-workflow into .gemini/skills/sensys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-workflow .github/skills/sensys-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 "sensys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-workflow into .github/skills/sensys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-workflow .opencode/skills/sensys-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 "sensys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-workflow into .opencode/skills/sensys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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
sensys-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 398 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and…
- Planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds
- SKILL.md covers Anchor the calendar first, Backward schedule from the…, Budget for the two-deadline… and Sequence the whole cycle, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Backward-scheduling so energy campaigns and long-term deployments finish before freeze
What it does
Sensys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and long-term deployments finish before freeze, budgeting time for the resubmission-with-revision path, and sequencing fit, building, writing, and submission.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Deployment and Budgeting and forecasting. 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 a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds
- Backward-scheduling so energy campaigns and long-term deployments finish before freeze
- Budgeting time for the resubmission-with-revision path
Example prompts
- “/sensys-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
Sensys Workflow loads about 1.2k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 398 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). 398 words, ~1,163 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-workflow/SKILL.md (or your agent's skills folder).- name
- sensys-workflow
- description
- Use when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and long-term deployments finish before freeze, budgeting time for the resubmission-with-revision path, and sequencing fit, building, writing, and submission.
SenSys Workflow
A SenSys campaign is governed by two facts the calendar imposes: SenSys runs two submission deadlines per cycle, and its evidence is physical, so the schedule is dominated by wall-clock time you cannot compress — a 47-day deployment takes 47 days. This skill turns the cycle into a backward schedule that leaves room for the measurements and, if needed, the resubmission.
Anchor the calendar first
Before scheduling anything, pin down against the live CFP and HotCRP /deadlines page:
- Which deadline you are targeting (first or second) and which edition it feeds. As of 2026-07-09 the open gate is SenSys 2027 (New York, May 10-13, 2027), with a first-round deadline of June 6, AoE; the second-round deadline is 待核实.
- The AoE cutoff, converted per coauthor.
- Whether an abstract-registration step precedes the paper upload this edition.
Treat the numbers here as a 2026-27 snapshot; the live page controls.
Backward schedule from the deadline
Deployment and energy campaigns, not writing, are the long pole. Schedule from T-0 (paper cutoff) backward:
| Phase | Window | What must be true by the end |
|---|---|---|
| Fit + framing | T-16 wk | sensys-topic-selection cleared; the system's claim is decided |
| Build + instrument | T-14 to T-8 wk | Hardware built, energy instrument set up, testbed reserved |
| Deployment / energy campaign | T-10 to T-4 wk | Long-term runs finished; traces captured (cannot compress) |
| Analysis + writing | T-6 to T-2 wk | Figures from real traces; body drafted against the worked example |
| Reproducibility freeze | T-3 wk | Provenance captured while the testbed is still live |
| Submission audit | T-1 wk to T-0 | sensys-submission end to end on the exact upload candidate |
The overlap is deliberate: writing starts while later deployment runs finish, because you cannot begin the 6-week deployment at T-4.
Show full SKILL.md (119 more words)Show less
Budget for the two-deadline reality
The two-deadline model changes planning in a way a single-deadline venue does not:
If targeting the FIRST deadline:
- A reject can resubmit at the SECOND deadline — but only WITH a substantive revision.
- Reserve testbed time AFTER the first notification for the new measurements a revision needs.
If targeting the SECOND deadline as a resubmission of a first-deadline reject:
- The revision + Response to Reviewers is REQUIRED, not optional (sensys-author-response).
- Back-schedule the new deployment/energy runs against the second cutoff BEFORE you commit.A blocking reviewer objection that needs a fresh energy-harvesting deployment cannot be answered
in two weeks — decide at notification whether the resubmission is feasible on the calendar, not
after you have already missed the window to start the runs (sensys-review-process).
Sequence the whole cycle
1. Fit → sensys-topic-selection (is it SenSys after the merger?)
2. Build → hardware + instrumentation; reserve the testbed
3. Measure → sensys-experiments + sensys-reproducibility (traces captured live)
4. Write → sensys-writing-style + sensys-supplementary + sensys-related-work
5. Submit → sensys-submission (audit the exact PDF; HotCRP fields verbatim)
6. Notification → sensys-review-process (classify), then:
accept → sensys-artifact-evaluation + sensys-camera-ready
resubmit → sensys-author-response, back-scheduled to the next deadlineStanding risks to track
- Testbed contention — shared hardware is the schedule's single point of failure; reserve early.
- Deployment failures — a node dying mid-run is normal; build slack for a re-run.
- Provenance loss — capture energy method and ground truth before teardown, not after.
- Edition drift — re-confirm which edition your deadline feeds each cycle; it can shift.
Output format
[Target] which deadline + which edition it feeds + AoE cutoff in local time
[Longpole] the deployment/energy campaign duration and its start-by date
[Schedule] backward plan T-0 → T-16wk with the freeze and audit points
[Resub] if a reject, is a next-deadline resubmission feasible on the calendar? Y/N
[Open] the scheduling risk most likely to break the plan© 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 SenSys-Skills/skills/sensys-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys 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 |
|---|---|---|---|---|---|---|
| Sensys Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Longbridge Researchhelsome/folio | 271 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Bet SizingJoelLewis/finance_skills | 206 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Cre Asset Managementahacker-1/cre-agent-skills | 113 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Dd LogsDataDog/pup | 1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Cash Flow ForecastWellApp-ai/Well | 345 | — | ~567 | Automated safety check: Pass | MIT |
Similar skills
Bet Sizing
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
Cre Asset Management
ahacker-1/cre-agent-skills
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions…
- Official
Dd Logs
DataDog/pup
Log management - search, pipelines, archives, and cost control.
Cash Flow Forecast
WellApp-ai/Well
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.
Cash Flow Snapshot
sandbaseai/sandbase-skills
Create a 30/60/90-day cash-flow forecast from AR, AP, opening cash, payment timing, and fixed-cost data.
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…
Related
Categories
Questions about Sensys Workflow
What does Sensys Workflow do?
A skill your agent uses when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and…. Sensys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and long-term deployments finish before freeze, budgeting time for the resubmission-with-revision path, and sequencing fit, building, writing, and submission.
When should I use Sensys Workflow?
Sensys Workflow fits situations like: planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds; backward-scheduling so energy campaigns and long-term deployments finish before freeze; budgeting time for the resubmission-with-revision path.
How do I install Sensys Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-workflow -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-workflow -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-workflow in your project. Codex loads it when a task matches its description.
Can I use Sensys 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 sensys-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/sensys-workflow, .gemini/skills/sensys-workflow, .github/skills/sensys-workflow and .opencode/skills/sensys-workflow in your project.
What does Sensys Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Sensys Workflow is instructions for the agent only.
Does Sensys 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 Sensys 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 Sensys Workflow use?
Sensys 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 Sensys Workflow use?
About 1.2k tokens (SKILL.md is roughly 4.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 Sensys Workflow?
Skills that share tags, products or a category with Sensys Workflow: Longbridge Research (helsome/folio, 271 stars), Bet Sizing (JoelLewis/finance_skills, 206 stars), Cre Asset Management (ahacker-1/cre-agent-skills, 113 stars) and Dd Logs (DataDog/pup, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sensys Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.