본문으로 건너뛰기
cccskills
무료GitHub에 공개

academic-research-journal

Use when evaluating, designing, drafting, revising, stress-testing, or preparing academic articles, empirical research reports, literature reviews, systematic reviews, meta-analyses, journal submissions, reviewer responses, research methods, sampling, measurement, analysis, publication readiness, or citation/source audits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(17)

  • SKILL.md5.1 KB
  • agent.md2.8 KB
  • agents/openai.yaml299 B
  • references/article-type-matrix.md4.5 KB
  • references/evidence-synthesis-and-review.md2.9 KB
  • references/integrity-and-source-audit.md3.2 KB
  • references/journal-readiness-scorecard.md3.4 KB
  • references/methods-evaluation-matrix.md6.6 KB
  • references/research-quality-principles.md3.9 KB
  • references/section-evaluation-matrix.md5.5 KB
  • scripts/manuscript_static_audit.py4.3 KB
  • tasks/design-research-project.md2.1 KB
  • tasks/evaluate-existing-work.md1.8 KB
  • tasks/evidence-synthesis.md1.9 KB
  • tasks/manuscript-production.md2.8 KB
  • tasks/revision-and-peer-review.md2.1 KB
  • tasks/source-and-reference-audit.md1.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Academic Research Journal

Core Rule

Evaluate and build academic work as a chain of claims: problem -> literature gap -> question -> design -> data -> measurement -> analysis -> interpretation -> contribution. Do not reward polish when the research logic is weak, and do not dismiss useful work merely because realistic constraints create limitations.

First Pass

  1. Classify the task: evaluate, design, draft, revise, review, respond to reviewers, audit sources, or plan evidence synthesis.
  2. Classify the article type: quantitative, qualitative, mixed methods, experimental, quasi-experimental, survey, field, case study, action research, policy/program evaluation, computational/big-data, literature review, systematic review, meta-analysis, theory, commentary, critique, or non-academic essay.
  3. Extract the research skeleton: problem, purpose, question, theory, population/case, sample/data, measures, design, analysis, findings, limitations, contribution, and claim strength.
  4. Identify the intended inference: exploratory insight, description, association, causality, mechanism, prediction, interpretation, policy/practice decision, or cumulative evidence.
  5. Define the evidence needed and mark gaps as I/I = insufficient information; mark inapplicable criteria as N/A.

Required Reads By Task

  • Existing paper, essay, or article evaluation: tasks/evaluate-existing-work.md, references/research-quality-principles.md, and references/journal-readiness-scorecard.md.
  • Article type or methods classification: references/article-type-matrix.md.
  • Section-level critique: references/section-evaluation-matrix.md.
  • Sampling, measures, experiments, qualitative, quantitative, mixed methods, survey, or program evaluation: references/methods-evaluation-matrix.md.
  • Literature review, systematic review, or meta-analysis: tasks/evidence-synthesis.md and references/evidence-synthesis-and-review.md.
  • Drafting a manuscript, essay, thesis chapter, or journal article: tasks/manuscript-production.md.
  • Research design or empirical validation planning: tasks/design-research-project.md.
  • Reviewer simulation, revision strategy, or response letter: tasks/revision-and-peer-review.md.
  • Reference, citation, source, ethics, or integrity audit: tasks/source-and-reference-audit.md and references/integrity-and-source-audit.md.

Evaluation Protocol

Use the 1-5 scale unless the user requests another format: 5 strong; 4 mostly strong; 3 adequate but limited; 2 major weaknesses; 1 invalid or not journal-ready; N/A; I/I.

Always evaluate fit between the claim and the method:

  • Generalization requires a defensible population, sampling frame, recruitment logic, response/nonresponse handling, and subgroup size.
  • Causal language requires random assignment, credible quasi-experimental logic, temporal ordering, comparison conditions, and confound control.
  • Measurement claims require conceptual definitions, operational alignment, reliability, validity, and bias mitigation.
  • Qualitative claims require design fit, sampling rationale, recruitment detail, coding transparency, reflexivity, context, triangulation or other credibility checks, and analyzed evidence.
  • Mixed methods claims require explicit design, clear strand roles, integration, value added, and handling of contradictory findings.
  • Evidence-synthesis claims require transparent search, inclusion/exclusion criteria, study quality/bias assessment, heterogeneity handling, and interpretable synthesis.

Evidence And Verification

  • Never invent sources, quotations, statistics, DOI links, journal facts, methods, datasets, reviewer comments, or results.
  • Current facts such as journal scope, instructions, rankings, indexing, impact factor, citation counts, reporting standards, and software versions need live verification.
  • Treat statistical significance as limited evidence; check magnitude, practical importance, sampling assumptions, model choice, robustness, and replication.
  • Treat missing methods detail as an evaluation finding, not permission to infer.
  • Separate evidence, inference, speculation, and recommendation.

Script Helper

  • Run scripts/manuscript_static_audit.py <file> for a heuristic scan of section coverage, overclaiming, missing limitations/ethics cues, significance-language risks, and reference signals.

Output Standard

Lead with the highest-impact judgment. Name assumptions, article type, intended inference, strongest contribution, fatal or major weaknesses, concrete fixes, and residual uncertainty. Use scorecards and claim-audit tables for evaluations; use manuscript architecture and section builders for drafting.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Android device offensive security, forensic extraction, and mobile app exploitation. Use this whenever the user needs to: break into or bypass the lock screen of an Android phone, extract data from a seized Android device for evidence, analyze or reverse-engineer an APK to find vulnerabilities, intercept communications on an Android device, exploit Android apps via deeplinks, steal crypto wallets or app data, set up rogue WiFi to target a phone, or plan any mobile device investigation or penetration test. Also trigger when the user mentions Android forensics, mobile pentesting, law enforcement phone extraction, device exploitation, WhatsApp or Telegram extraction from a phone, Android app reversing, CVE research for Android, or needing a chain of custody for mobile evidence. Even if the user describes the scenario casually or in another language, if they need to gain access to or pull data from an Android phone, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

oghie/skillsets92026년 10월 3일 업데이트

Use when performing cybersecurity operations - offensive or defensive - including threat detection and hunting, SOC operations, incident response, digital forensics and DFIR, malware analysis and reverse engineering, threat intelligence, cloud/container/network/application/API security, identity-access and zero-trust, OT/ICS and endpoint security, vulnerability and supply-chain management, DevSecOps, cryptography, AI security, compliance and governance, and red-team or penetration testing under signed rules of engagement; routes to one of 800+ technique playbooks mapped to MITRE ATT&CK, D3FEND, and NIST CSF.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

oghie/skillsets92026년 10월 3일 업데이트

Use when designing, reviewing, modifying, migrating, optimizing, securing, operating, troubleshooting, or decommissioning data architectures across data model exploration, SQL, ISO SQL conformance, NoSQL, vector, graph, document, time-series, NewSQL, search, in-memory, SQLite, CDC/Debezium, DBMS storage/query/recovery internals, database incident prevention, hardware acceleration, cache, big-data, lakehouse, and warehouse systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

oghie/skillsets92026년 10월 3일 업데이트

Use when developing, reviewing, debugging, porting, or engineering Linux kernel device drivers, kernel modules, device tree bindings, bus clients, subsystem drivers, DMA/IRQ/memory paths, userspace interfaces, or hardware bring-up plans.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

oghie/skillsets92026년 10월 3일 업데이트

Use when designing, implementing, reviewing, debugging, testing, profiling, or porting concurrent, parallel, distributed, high-performance, network dataplane, kernel-bypass, or real-time software, including locks, semaphores, monitors, MPI, CSP rendezvous, DPDK, VPP, eBPF, XDP, AF_XDP, SR-IOV, RSS, RoCEv2/RDMA, RMS/EDF, priority inversion, and environment selection from silicon to edge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

oghie/skillsets92026년 10월 3일 업데이트

Use when designing, evaluating, documenting, modernizing, reviewing, refactoring, or implementing software architecture and code-level structure, including requirements, context, architecture style selection, microservices patterns, WebAssembly/WASI/Component Model, UMA portable capabilities, runtime contracts, capability graphs, governed MCP/agent orchestration, clean code, code smells, Rust crate/library API architecture, Cargo feature/MSRV/SemVer policy, unsafe/FFI/no_std/library testing, modularity, views, NFR tactics, IAM/auth, security patterns, cost estimation, architecture-as-code fitness functions, ADR/RFC work, and engineering execution plans.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

oghie/skillsets92026년 10월 3일 업데이트

oghie의 스킬 모두 보기

이 스킬의 문제 신고