SkillHub ClubShip Full StackFull Stack

extract-algorithm

Imported from https://github.com/mvillmow/ProjectOdyssey.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C3.9

Composite score

3.9

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install mvillmow-projectodyssey-extract-algorithm

Repository

mvillmow/ProjectOdyssey

Skill path: .claude/skills/tier-2/extract-algorithm

Imported from https://github.com/mvillmow/ProjectOdyssey.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: mvillmow.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install extract-algorithm into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/mvillmow/ProjectOdyssey before adding extract-algorithm to shared team environments
Use extract-algorithm for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: extract-algorithm
description: "Parse and document algorithm pseudocode from research papers. Use when preparing for implementation."
mcp_fallback: none
category: analysis
tier: 2
---

# Extract Algorithm

Identify, document, and translate algorithms from research papers into structured pseudocode for implementation planning.

## When to Use

- Converting paper algorithms to code
- Understanding computational complexity
- Planning implementation steps
- Documenting algorithm variations

## Quick Reference

```bash
# Extract text from PDF focusing on algorithms
pdftotext paper.pdf - | grep -A 20 -i "algorithm\|pseudocode" | head -50

# Convert pseudo-code to structured documentation
# Use cleaner formatting with numbered steps
```

## Workflow

1. **Locate algorithm**: Find algorithm description, pseudocode, or flowchart in paper
2. **Document steps**: Extract numbered steps or pseudocode from paper
3. **Identify inputs/outputs**: List parameters, preconditions, postconditions
4. **Note special cases**: Document edge cases and conditional logic
5. **Translate to implementation plan**: Convert to implementation checklist

## Output Format

Algorithm documentation:

- Algorithm name and source reference
- Inputs (parameters, data types, constraints)
- Outputs (return values, side effects)
- Pseudocode or step-by-step description
- Complexity analysis (time and space)
- Special cases and error handling
- Implementation notes and tips

## References

- See `analyze-equations` skill for mathematical formula extraction
- See `identify-architecture` skill for understanding algorithm structure
- See CLAUDE.md > Key Development Principles for implementation guidance