Individual skill
sensys-writing-style
Use when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit, putting the buildable system on the first page, reporting energy and latency as numbers not adjectives, and pairing every claim with a measurement.
SenSys-Skills/skills/sensys-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,409
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,326 bytes
Read excerpt
# SenSys Writing Style
A SenSys paper reads as an engineer's argument: here is a sensing or embedded problem that hurts
in a specific way, here is why existing systems fail on constrained hardware, here is the
mechanism I built, and here is its measured behavior. The house style rewards concreteness —
energy in joules, latency in a distribution, uptime in days — and penalizes the adjective
("lightweight," "efficient") that stands in for a measurement.
## The first-page arc
Put the system on the first page. The abstract and opening paragraph should already carry:
1. **The sensing/deployment pain** — the physical problem, stated so a systems reader feels it.
2. **Why existing systems fail** — each prior approach's failure named specifically, in embedded