Przejdź do treści
Biblioteka skilli
Nauka i badania · Analiza

methodology-extractor

/methodology-extractor

Wyciąga metody eksperymentalne z jednej lub wielu publikacji do ustrukturyzowanego streszczenia protokołu, przydatnego do porównań i opisu powtarzalnych procedur.

Licencja
MIT
Ostatnia zmiana repozytorium
17.09.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
2
Przestarzałość

Brak sygnałów. Repozytorium zmienione 17.09.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/main.py

Co robi i kiedy

Wyciąga metody eksperymentalne z jednej lub wielu publikacji do ustrukturyzowanego streszczenia protokołu, przydatnego do porównań i opisu powtarzalnych procedur.

Oryginalny opis (EN)

Extract experimental methods from one or more papers into a structured protocol-oriented summary; use when comparing methods across studies or drafting reproducible procedures.

Jak działa

  1. Quick Check
  2. Audit-Ready Commands
  3. When to Use
  4. Workflow
  5. Use Cases
  6. Parameters
  7. Returns
  8. Example
  9. Risk Assessment
  10. Security Checklist
Sekcje z nagłówków SKILL.md, w oryginale · 186 linii, 1 145 słów
Podgląd SKILL.md
---
name: methodology-extractor
description: Extract experimental methods from one or more papers into a structured protocol-oriented summary; use when comparing methods across studies or drafting reproducible procedures.
license: MIT
author: AIPOCH
---
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)

# Methodology Extractor

Extract and compare experimental protocols across papers.

## Quick Check

Use this command to verify that the packaged script entry point can be parsed before deeper execution.

```bash
python -m py_compile scripts/main.py
```

## Audit-Ready Commands

Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.

```bash
python -m py_compile scripts/main.py
python scripts/main.py --help
```

## When to Use

- Use this skill when the task needs Batch extraction of experimental methods from multiple papers for protocol.
- Use this skill for evidence insight tasks that require explicit assumptions, bounded scope, and a reproducible output format.
- Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.

## Workflow

1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
2. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
3. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
4. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
5. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.

## Use Cases
- Protocol optimization
- Methods comparison for systematic reviews
- Reproducibility assessment

## Parameters
- `paper_ids`: List of papers to analyze
- `method_type`: Target method (e.g., "Western Blot", "qPCR")

## Returns
- Comparison table of protocols
- Parameter variations across studies
- Best practice recommendations

## Example
Input: 50 papers, method_type="Western Blot"
Output: Table showing antibody concentrations, blocking conditions, wash times

## Risk Assessment

| Risk Indicator | Assessment | Level |
|----------------|------------|-------|
| Code Execution | Python/R scripts executed locally | Medium |
| Network Access | No external API calls | Low |
| File System Access | Read input files, write output files | Medium |
| Instruction Tampering | Standard prompt guidelines | Low |
| Data Exposure | Output files saved to workspace | Low |

## Security Checklist

- [ ] No hardcoded credentials or API keys
- [ ] No unauthorized file system access (../)
- [ ] Output does not expose sensitive information
- [ ] Prompt injection protections in place
- [ ] Input file paths validated (no ../ traversal)
- [ ] Output directory restricted to workspace
- [ ] Script execution in sandboxed environment
- [ ] Error messages sanitized (no stack traces exposed)
- [ ] Dependencies audited

## Prerequisites

No additional Python packages required.

## Evaluation Criteria

### Success Metrics
- [ ] Successfully executes main functionality
- [ ] Output meets quality standards
- [ ] Handles edge cases gracefully
- [ ] Performance is acceptable

### Test Cases
1. **Basic Functionality**: Standard input → Expected output
2. **Edge Case**: Invalid input → Graceful error handling
3. **Performance**: Large dataset → Acceptable processing time

## Lifecycle Status

- **Current Stage**: Draft
- **Next Review Date**: 2026-03-06
- **Known Issues**: None
- **Planned Improvements**: 
  - Performance optimization
  - Additional feature support

## Output Requirements

Every final response should make these items explicit when they are relevant:

- Objective or requested deliverable
- Inputs used and assumptions introduced
- Workflow or decision path
- Core result, recommendation, or artifact
- Constraints, risks, caveats, or validation needs
- Unresolved items and next-step checks

## Error Handling

- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
- If `scripts/main.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
- Do not fabricate files, citations, data, search results, or execution outcomes.

## Input Validation

This skill accepts requests that match the documented purpose of `methodology-extractor` and include enough context to complete the workflow safely.

Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:

> `methodology-extractor` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.


## References

- [references/audit-reference.md](references/audit-reference.md) - Supported scope, audit commands, and fallback boundaries

## Response Template

Use the following fixed structure for non-trivial requests:

1. Objective
2. Inputs Received
3. Assumptions
4. Workflow
5. Deliverable
6. Risks and Limits
7. Next Checks

If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.

## When Not to Use

- Do not proceed when required input files, identifiers, parameters, or context are missing — ask the user to provide them first.
- Do not assume capabilities beyond this skill's declared scope when the user requests external operations or inferences.
- Do not proceed without user confirmation when overwriting existing results, executing high-cost batch operations, or expanding task scope.

## Required Inputs

| Field | Required | Format/Source | Example | If Missing |
|---|---|---|---|---|
| User task description | Yes | Text | Research question, writing goal, analysis objective | Stop and ask user to provide |
| Primary input material | Depends on task | Text, file path, ID, table, or literature | PMID, PDF, CSV, DOCX, keywords, etc. | Specify which material type is missing |
| Output preference | No | Text | Language, format, target journal, template | Use skill default format |

## Output Contract

- Primary output: Structured result or target file aligned with this skill's objective.
- Optional output: Intermediate check notes, issue list, supplementary suggestions, or generated file paths.
- Format requirement: Unless the user specifies otherwise, prefer stable, reviewable Markdown or JSON; if the skill's bundled script requires a fixed format, use that format.
- If partially complete: Must explicitly mark as PARTIAL and state which steps are completed and which remain.

## Failure Handling

- Missing critical input: Explicitly state which fields, files, or identifiers are missing and pause.
- Script, template, or resource execution failure: Report the failing step, likely cause, and recovery suggestions — do not silently degrade.
- Partial completion only: Return the verified portion first, then list remaining blockers and suggested next steps.

## User Checkpoints

- Before executing batch processing, overwriting files, long-running searches, or multi-stage generation, confirm scope and output format with the user.
- Before proceeding when a key judgment is ambiguous, evidence is insufficient, or the workflow is entering the next stage, confirm with the user.

## Quick Validation

- Check that key scripts, templates, or reference file paths this skill depends on exist.
- Check that the final output contains the core fields, sections, or files specified for this task.
- Check that results clearly mark assumptions, limitations, and incomplete items.
Pliki w paczce (5)
  • POLISH_CHANGELOG.md 1 KB
  • SKILL.md 8 KB
  • eval_report_methodology-extractor_result.json 11 KB
  • references/audit-reference.md 1 KB
  • scripts/main.py 4 KB

Wersje

W bazie nie ma innych skilli o nazwie methodology-extractor.

Migawka bazy z 13.11.2026 · wersja paczki c864e63d3a54 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100scientific-literature-researcher
    Przeszukuje literaturę naukową i wyciąga z pełnych tekstów dane eksperymentalne, np. metody, wyniki i liczebność prób.
  • 100methodology-extraction
    Wydobywa szczegółowy, odtwarzalny opis metodologii użytej w dokumencie badawczym i klasyfikuje, na ile ta metodologia jest odtwarzalna.
  • 98pdf-extract-experimental-materials
    Wyciąga materiały eksperymentalne i informacje o aparaturze z plików PDF do trzech tabel CSV, z sekcji takich jak Materials and Methods, Key Resources Table, odczynniki, przeciwciała i sprzęt.
  • 100scientific-literature-researcher
    Przeszukuje literaturę naukową i pobiera uporządkowane dane eksperymentalne z opublikowanych badań: metody, wyniki, liczebność prób i oceny jakości, z odpowiedziami opartymi na pełnych tekstach.
  • 100alterlab-bgpt-search
    Wyszukuje artykuły naukowe przez serwer MCP BGPT i zwraca ustrukturyzowane dane eksperymentalne z pełnych tekstów, takie jak metody, wyniki i liczebność prób.
  • 100bgpt-paper-search
    Wyszukuje artykuły naukowe przez serwer MCP BGPT i zwraca uporządkowane dane eksperymentalne z pełnych tekstów: metody, wyniki, liczebność próby, oceny jakości i wnioski, przydatne w przeglądach literatury.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.