Skip to content
Skills Library
Science & research · Writing

electronics-lab-report

/electronics-lab-report

Create, revise, and quality-check electronics and electrical-engineering laboratory reports, especially Korean circuit experiment result reports. Use when users provide lab handouts, measured data, waveforms, tables, photos, or DOCX files and ask for a report, natural academic Korean, calculations, measured-vs-calculated table checks, or Word rendering/page inspection. Preserve measurements, units, equations, component labels, and source evidence; follow course-specific templates before any defaults.

Licence
MIT
Last repository change
06.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create, revise, and quality-check electronics and electrical-engineering laboratory reports, especially Korean circuit experiment result reports. Use when users provide lab handouts, measured data, waveforms, tables, photos, or DOCX files and ask for a report, natural academic Korean, calculations, measured-vs-calculated table checks, or Word rendering/page inspection. Preserve measurements, units, equations, component labels, and source evidence; follow course-specific templates before any defaults.

Original author description

Create, revise, and quality-check electronics and electrical-engineering laboratory reports, especially Korean circuit experiment result reports. Use when users provide lab handouts, measured data, waveforms, tables, photos, or DOCX files and ask for a report, natural academic Korean, calculations, measured-vs-calculated table checks, or Word rendering/page inspection. Preserve measurements, units, equations, component labels, and source evidence; follow course-specific templates before any defaults.

How it works

  1. Load the relevant guidance
  2. Workflow
  3. Hard stops
  4. Optional checks (when execution is available)
Original SKILL.md headings · 42 lines, 614 words
SKILL.md preview
---
name: electronics-lab-report
description: Create, revise, and quality-check electronics and electrical-engineering laboratory reports, especially Korean circuit experiment result reports. Use when users provide lab handouts, measured data, waveforms, tables, photos, or DOCX files and ask for a report, natural academic Korean, calculations, measured-vs-calculated table checks, or Word rendering/page inspection. Preserve measurements, units, equations, component labels, and source evidence; follow course-specific templates before any defaults.
---

# Electronics Lab Report

Produce accurate, readable electronics-lab reports without inventing experimental evidence. Preserve technical meaning before improving style. Follow the user's report format, assignment sheet, and verified results before general conventions.

## Load the relevant guidance

- **Creating or evaluating a full report:** Read `references/report-standards.md`.
- **Polishing Korean writing:** Read `references/korean-humanization.md`.
- **Editing, exporting, or reviewing Word (`.docx`):** Read `references/word-render-qa.md`.
- **Attribution, license:** See `references/NOTICE.md`.

Only load the references needed for the request.

## Workflow

1. **Determine scope.** Distinguish (a) prose-only polishing, (b) report drafting from source data, (c) data/calculation audit, and (d) Word generation or quality review. Do not rewrite an entire report when the request concerns only one section.
2. **Collect evidence and constraints.** Read the lab handout, user's measurements, photographs, supplied prior-report template, and requested output format. Identify which fields are measured, calculated, theoretical, or inapplicable based on the handout—not on mathematical convenience. If an essential source is absent, ask for it or use an explicit blank/placeholder; never invent a reading, experiment date, part model, procedure, result, or photo.
3. **Freeze protected technical content.** Preserve signs, numeric precision, units, equations, variables/subscripts, component and instrument identifiers, circuit nodes, conditions, table/figure IDs, experiment dates, and the uncertainty level of statements. Technical correction is a separate, clearly identified operation; never silently 'fix' a recorded measurement.
4. **Honor the course's structure first.** Reproduce provided table shapes, labels, row/column roles, measured/calculated placement, image requirements, and report styling. If the course has no format, use a clean conventional electronics lab format; never impose one school's font, cover-page policy, or blank-cell marker on everybody.
5. **Write or edit with appropriate intensity.** Use minimal edits for methods/results and more fluid but evidence-grounded Korean for discussion. Describe experimental procedure only as supported. Discuss observed trend -> circuit theory -> uncertainty/possible error without making unverified causes sound certain.
6. **Reconcile calculations and tables.** Include formula, substitution, units, and result for each required condition. Where the handout requires a computed table cell, verify the number actually appears **in that DOCX table cell**. Do not treat a calculation written beneath a table as completing an empty cell. If a measurement and calculated value conflict, flag rather than overwrite without user authorization.
7. **If producing or revising a DOCX, render -> inspect every page -> fix -> re-render.** Inspect text and tables structurally as well as visually. Use the document tooling available in the execution environment and the utilities in `scripts/` when suitable. If rendering or page inspection is unavailable, disclose that the visual inspection was not completed; do not claim it passed.
8. **Return the requested deliverable and minimal notes.** Provide the requested full text, DOCX, or review. Clearly distinguish verified issues from suggestions and unverified assumptions.

## Hard stops

- Never synthesize experimental measurements or report that a circuit was physically tested when no test data were provided.
- Never substitute predicted values for measured values, or assign a 'calculated' category to a field merely because it can be computed mathematically.
- Never change equation symbols, sign conventions, frequencies, tolerances, units, component models, or significant figures for style.
- Never claim that prose edits evade AI detectors or guarantee authenticity scores.
- Never claim that Word layout was visually inspected without viewing the rendered pages.

## Optional checks (when execution is available)

```bash
python scripts/check_preservation.py original.txt revised.txt
python scripts/inspect_docx.py report.docx --expect examples/expected-cells.example.json
python scripts/render_docx.py report.docx --output_dir qa-pages --emit_pdf
```

Treat these as **aids**, not as proof: token comparison cannot validate all electronics theory; table inspection cannot detect visual clipping; rendering cannot prove that values are experimentally correct. For rendering, actually open and inspect **every** `qa-pages/page-*.png` image. Inspecting the rendered pages is a human/visual-agent action, not an automatic property of the renderer.
Files in this package (5)
  • .gitignore 1 KB
  • LICENSE 1 KB
  • LICENSE-im-not-ai.txt 1 KB
  • README.md 7 KB
  • SKILL.md 5 KB

Versions

The database has no other skills named electronics-lab-report.

Database snapshot: 13.11.2026 · package version ab168bb5eea7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90electrical
    Electrical and electronics engineering research. Use when the user invokes /electrical or asks about electrical engineering topics — power systems, electronics, circuit design, controls, signal integrity, EMC, motors and drives, grid and renewables — or asks to verify an…
  • 100ai-graded-lab-report
    当需要按学校模板撰写、改写或终检由 AI 评阅系统打分的大学物理实验报告时使用:输入教材、课件与上次评阅反馈,复制模板生成初稿,再按证据清单迭代;适用于中文 DOCX、不确定度、图表与数据处理场景。v1.3.0 另含可选的教学平台上传脚本(先预览、确认后才写服务器)。
  • 95lab-weekly-report
    Search accessible agent chat history, verify a lab member's weekly and Gantt-chart progress, and create natural, author-approved Markdown and PDF reports with learning reflections and optional task images. Use when drafting, reviewing, or generating a laboratory weekly report.
  • 91latex-academic-reports
    Generate academic reports, papers, and technical documentation using LaTeX. Use when the user asks to create research papers, lab reports, theses, technical documentation, IEEE-style papers, or any academic document requiring professional typesetting. Produces…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.