원클릭으로 Manus에서 모든 스킬 실행

report-in-markdown

Markdown style guide for agents writing PLAN.md, RESULTS.md, status reports, or standalone markdown reports, with optional references for figures, LaTeX math, and tables.

Manus에서 실행

개요

Markdown style guide for agents writing PLAN.md, RESULTS.md, status reports, or standalone markdown reports, with optional references for figures, LaTeX math, and tables.

설치 명령

npx skills add https://github.com/FuZhiyu/superRA --skill report-in-markdown

이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요

출처

FuZhiyu/superRA

스타3

포크1

업데이트2026년 5월 30일 19:03

파일 탐색기

4 개 파일

SKILL.md

readonly

name	report-in-markdown
description	Markdown style guide for agents writing PLAN.md, RESULTS.md, status reports, or standalone markdown reports, with optional references for figures, LaTeX math, and tables.
user-invocable	true

Report in Markdown

The markdown style guide for any agent writing markdown. Use the rule below for source-file citations; load references only when the output needs figures, LaTeX math, tables, or final-form RESULTS.md guidance.

File-reference rule

Cite source files as markdown links with line anchors, not backtick-wrapped paths.

Use case	Form
Single line	file.py:42
Line range	file.py:40-50
Whole file	file.py

Resolve paths relative to the markdown file's directory (use ../ as needed). For files at the worktree root, the relative path equals the project-root path.

Load map

Caller	Load
Implementer / reviewer writing routine task-block citations only	nothing beyond this file
Implementer writing a `RESULTS.md` task section with figures / math / tables	`rich-content.md`
`superintegrate` Document doc-writer subagent	`baseline-io.md` + `rich-content.md` + `final-form.md`
`superintegrate` Document doc-reviewer subagent	`final-form.md`
Standalone markdown report (any context)	`baseline-io.md` + `rich-content.md`

The attachments/ directory is a caller parameter; defaults and fallbacks are in references/rich-content.md §Figures.

References

references/baseline-io.md — frontmatter spec, filename convention, output-path resolution. Permanent artifacts only.
references/rich-content.md — figure handling (PDF→PNG, relative-path embedding), LaTeX math, markdown tables.
references/final-form.md — final RESULTS.md consolidation: fact-check checklist, task-indexed → reader-facing restructure, figure materialization, relocation.

이 저장소의 다른 Skills

같은 저장소

agent-orchestration

FuZhiyu/superRA

Requires `superRA:using-superra` loaded first. Use when dispatching agents in the superRA workflow. Triggers include "dispatch N agents", "run these in parallel", "who should do the review", a multi-step workflow that needs coordination across roles, or a session handoff where workflow state must survive. Usable in any phase of the superRA workflow (PLAN / IMPLEMENT / INTEGRATE).

2026-05-303

econ-data-analysis

FuZhiyu/superRA

Use PROACTIVELY whenever performing data analysis on economic, financial, or panel datasets — importing raw data, cleaning, merging, filtering, constructing variables, aggregating, computing summary statistics, producing regression inputs, building figures, or writing analysis scripts. Triggers include panel data, "merge these datasets", "run regression", "clean this data", "construct variable X", "check the summary stats", or any data file with unknown structure. Language-agnostic (Python, Julia, R, Stata).

2026-05-303

handoff-doc

FuZhiyu/superRA

Use whenever creating a PLAN.md / RESULTS.md from scratch, maturing RESULTS.md into its permanent record at INTEGRATE, or when you need the full editing discipline for a task-block-structured handoff document. Carries the four document principles, the inline-edit rule, the stale-content checklist, and pointers to full PLAN.md / RESULTS.md anatomy templates. Usable standalone by a single author with no subagents — the author plays all roles and reads this skill directly. Doc-creation call sites: `superplan` Phase 2 (new plan + RESULTS.md skeleton) and `superintegrate` Step 3 doc-writer (Stage 2 maturation).

2026-05-303

refactor-and-integrate

FuZhiyu/superRA

Utility skill (any phase). Use when refactoring analysis code for codebase integration, reviewing post-sync branch quality, auditing project docs, pruning a governing diff to minimum net diff, or using task-local Sync impact context as justification evidence. Carries the Codebase Integration checklist shared by implementer (self-check before commit) and reviewer (verification). Standalone-invokable outside the full integration workflow for any refactor that needs consistent quality gates.

2026-05-303

semantic-merge

FuZhiyu/superRA

Use when about to run `git merge`, `git rebase`, or `git cherry-pick`; when syncing a feature, analysis, or work branch with a current base branch before integration; or when incoming changes may touch results-bearing files, source scripts, PLAN.md, RESULTS.md, drift tests, or domain-discipline artifacts. Triggers include: bare `git merge` / `git rebase` / `git cherry-pick` (the merge-guard hook flags these automatically), "sync with main", "pull main into this branch", "rebase onto main", "cherry-pick commit X", or any branch integration where conflict resolution must preserve the intent behind each side. Invoked by `superintegrate` during Sync and usable standalone by any agent or human doing an intent-aware branch integration.

2026-05-303

superimplement

FuZhiyu/superRA

Requires `superRA:using-superra` loaded first. Use when you have a PLAN.md in the superRA task-block format and are ready to implement its tasks; when a plan has been approved and you need per-task implementation with an implementer-reviewer pair; when resuming work on a plan where some tasks are `IMPLEMENTED`, some `REVISE`, and some not started; when an analysis is code-complete and you want to verify reproducibility and present completion options (merge / PR / keep / discard). Triggers include "execute the plan", "run task N", "implement this PLAN.md", "finish this analysis", a branch with an APPROVED plan but no code yet, or a REVISE state that needs orchestrator adjudication before re-dispatch.

2026-05-303

출처

FuZhiyu

FuZhiyu/superRA

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

유용한 대상SOC

기술 작가예술, 디자인, 엔터테인먼트, 스포츠, 미디어직27-3042L4

name	report-in-markdown
description	Markdown style guide for agents writing PLAN.md, RESULTS.md, status reports, or standalone markdown reports, with optional references for figures, LaTeX math, and tables.
user-invocable	true

Report in Markdown

File-reference rule

Cite source files as markdown links with line anchors, not backtick-wrapped paths.

Use case	Form
Single line	file.py:42
Line range	file.py:40-50
Whole file	file.py

Resolve paths relative to the markdown file's directory (use ../ as needed). For files at the worktree root, the relative path equals the project-root path.

Load map

Caller	Load
Implementer / reviewer writing routine task-block citations only	nothing beyond this file
Implementer writing a `RESULTS.md` task section with figures / math / tables	`rich-content.md`
`superintegrate` Document doc-writer subagent	`baseline-io.md` + `rich-content.md` + `final-form.md`
`superintegrate` Document doc-reviewer subagent	`final-form.md`
Standalone markdown report (any context)	`baseline-io.md` + `rich-content.md`

The attachments/ directory is a caller parameter; defaults and fallbacks are in references/rich-content.md §Figures.

References

references/baseline-io.md — frontmatter spec, filename convention, output-path resolution. Permanent artifacts only.
references/rich-content.md — figure handling (PDF→PNG, relative-path embedding), LaTeX math, markdown tables.
references/final-form.md — final RESULTS.md consolidation: fact-check checklist, task-indexed → reader-facing restructure, figure materialization, relocation.