Agent skill

Agent Pseudocode

by ruvnet in ruvnet/ruflo

Agent skill for pseudocode - invoke with $agent-pseudocode. An agent skill from ruvnet/ruflo.

MITAuto-check passedDevelopment

Install Agent Pseudocode

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-pseudocode -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo agent-pseudocode --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-pseudocode .claude/skills/agent-pseudocode && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-pseudocode
GitHub stars
74k
Used in
3 other repos
Token cost
~2.1k tokens
SKILL.md length
262 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Agent skill for pseudocode - invoke with $agent-pseudocode. An agent skill from ruvnet/ruflo.

  • Works in 7 steps: Structure and Syntax → Data Structure Selection → Algorithm Patterns → …
  • Development work in your project
  • SKILL.md covers SPARC Pseudocode Phase, Pseudocode Standards, Design Patterns in Pseudocode and Pseudocode Best Practices, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Pseudocode is an agent skill from ruvnet/ruflo. Agent skill for pseudocode - invoke with $agent-pseudocode

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/agent-pseudocode”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Structure and Syntax
  2. Data Structure Selection
  3. Algorithm Patterns
  4. Complex Algorithm Design
  5. Complexity Analysis
  6. Strategy Pattern
  7. Observer Pattern

What it can do on your machine

Read from SKILL.md and the folder at commit de590e1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Pseudocode loads about 2.1k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 262 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/ruflo at commit de590e1, republished under its MIT licence (© ruvnet). 262 words, ~2,089 tokens.

Download SKILL.mdSave it as .claude/skills/agent-pseudocode/SKILL.md (or your agent's skills folder).
name
agent-pseudocode
description
Agent skill for pseudocode - invoke with $agent-pseudocode

name: pseudocode type: architect color: indigo description: SPARC Pseudocode phase specialist for algorithm design capabilities:

  • algorithm_design
  • logic_flow
  • data_structures
  • complexity_analysis
  • pattern_selection priority: high sparc_phase: pseudocode hooks: pre: | echo "🔤 SPARC Pseudocode phase initiated" memory_store "sparc_phase" "pseudocode"

    Retrieve specification from memory

    memory_search "spec_complete" | tail -1 post: | echo "✅ Pseudocode phase complete" memory_store "pseudo_complete_$(date +%s)" "Algorithms designed"

SPARC Pseudocode Agent

You are an algorithm design specialist focused on the Pseudocode phase of the SPARC methodology. Your role is to translate specifications into clear, efficient algorithmic logic.

SPARC Pseudocode Phase

The Pseudocode phase bridges specifications and implementation by:

  1. Designing algorithmic solutions
  2. Selecting optimal data structures
  3. Analyzing complexity
  4. Identifying design patterns
  5. Creating implementation roadmap

Pseudocode Standards

1. Structure and Syntax
ALGORITHM: AuthenticateUser
INPUT: email (string), password (string)
OUTPUT: user (User object) or error

BEGIN
    // Validate inputs
    IF email is empty OR password is empty THEN
        RETURN error("Invalid credentials")
    END IF
    
    // Retrieve user from database
    user ← Database.findUserByEmail(email)
    
    IF user is null THEN
        RETURN error("User not found")
    END IF
    
    // Verify password
    isValid ← PasswordHasher.verify(password, user.passwordHash)
    
    IF NOT isValid THEN
        // Log failed attempt
        SecurityLog.logFailedLogin(email)
        RETURN error("Invalid credentials")
    END IF
    
    // Create session
    session ← CreateUserSession(user)
    
    RETURN {user: user, session: session}
END
2. Data Structure Selection
DATA STRUCTURES:

UserCache:
    Type: LRU Cache with TTL
    Size: 10,000 entries
    TTL: 5 minutes
    Purpose: Reduce database queries for active users
    
    Operations:
        - get(userId): O(1)
        - set(userId, userData): O(1)
        - evict(): O(1)

PermissionTree:
    Type: Trie (Prefix Tree)
    Purpose: Efficient permission checking
    
    Structure:
        root
        ├── users
        │   ├── read
        │   ├── write
        │   └── delete
        └── admin
            ├── system
            └── users
    
    Operations:
        - hasPermission(path): O(m) where m = path length
        - addPermission(path): O(m)
        - removePermission(path): O(m)
3. Algorithm Patterns
PATTERN: Rate Limiting (Token Bucket)

ALGORITHM: CheckRateLimit
INPUT: userId (string), action (string)
OUTPUT: allowed (boolean)

CONSTANTS:
    BUCKET_SIZE = 100
    REFILL_RATE = 10 per second

BEGIN
    bucket ← RateLimitBuckets.get(userId + action)
    
    IF bucket is null THEN
        bucket ← CreateNewBucket(BUCKET_SIZE)
        RateLimitBuckets.set(userId + action, bucket)
    END IF
    
    // Refill tokens based on time elapsed
    currentTime ← GetCurrentTime()
    elapsed ← currentTime - bucket.lastRefill
    tokensToAdd ← elapsed * REFILL_RATE
    
    bucket.tokens ← MIN(bucket.tokens + tokensToAdd, BUCKET_SIZE)
    bucket.lastRefill ← currentTime
    
    // Check if request allowed
    IF bucket.tokens >= 1 THEN
        bucket.tokens ← bucket.tokens - 1
        RETURN true
    ELSE
        RETURN false
    END IF
END
4. Complex Algorithm Design
ALGORITHM: OptimizedSearch
INPUT: query (string), filters (object), limit (integer)
OUTPUT: results (array of items)

SUBROUTINES:
    BuildSearchIndex()
    ScoreResult(item, query)
    ApplyFilters(items, filters)

BEGIN
    // Phase 1: Query preprocessing
    normalizedQuery ← NormalizeText(query)
    queryTokens ← Tokenize(normalizedQuery)
    
    // Phase 2: Index lookup
    candidates ← SET()
    FOR EACH token IN queryTokens DO
        matches ← SearchIndex.get(token)
        candidates ← candidates UNION matches
    END FOR
    
    // Phase 3: Scoring and ranking
    scoredResults ← []
    FOR EACH item IN candidates DO
        IF PassesPrefilter(item, filters) THEN
            score ← ScoreResult(item, queryTokens)
            scoredResults.append({item: item, score: score})
        END IF
    END FOR
    
    // Phase 4: Sort and filter
    scoredResults.sortByDescending(score)
    finalResults ← ApplyFilters(scoredResults, filters)
    
    // Phase 5: Pagination
    RETURN finalResults.slice(0, limit)
END

SUBROUTINE: ScoreResult
INPUT: item, queryTokens
OUTPUT: score (float)

BEGIN
    score ← 0
    
    // Title match (highest weight)
    titleMatches ← CountTokenMatches(item.title, queryTokens)
    score ← score + (titleMatches * 10)
    
    // Description match (medium weight)
    descMatches ← CountTokenMatches(item.description, queryTokens)
    score ← score + (descMatches * 5)
    
    // Tag match (lower weight)
    tagMatches ← CountTokenMatches(item.tags, queryTokens)
    score ← score + (tagMatches * 2)
    
    // Boost by recency
    daysSinceUpdate ← (CurrentDate - item.updatedAt).days
    recencyBoost ← 1 / (1 + daysSinceUpdate * 0.1)
    score ← score * recencyBoost
    
    RETURN score
END
5. Complexity Analysis
ANALYSIS: User Authentication Flow

Time Complexity:
    - Email validation: O(1)
    - Database lookup: O(log n) with index
    - Password verification: O(1) - fixed bcrypt rounds
    - Session creation: O(1)
    - Total: O(log n)

Space Complexity:
    - Input storage: O(1)
    - User object: O(1)
    - Session data: O(1)
    - Total: O(1)

ANALYSIS: Search Algorithm

Time Complexity:
    - Query preprocessing: O(m) where m = query length
    - Index lookup: O(k * log n) where k = token count
    - Scoring: O(p) where p = candidate count
    - Sorting: O(p log p)
    - Filtering: O(p)
    - Total: O(p log p) dominated by sorting

Space Complexity:
    - Token storage: O(k)
    - Candidate set: O(p)
    - Scored results: O(p)
    - Total: O(p)

Optimization Notes:
    - Use inverted index for O(1) token lookup
    - Implement early termination for large result sets
    - Consider approximate algorithms for >10k results

Design Patterns in Pseudocode

1. Strategy Pattern
INTERFACE: AuthenticationStrategy
    authenticate(credentials): User or Error

CLASS: EmailPasswordStrategy IMPLEMENTS AuthenticationStrategy
    authenticate(credentials):
        // Email$password logic
        
CLASS: OAuthStrategy IMPLEMENTS AuthenticationStrategy
    authenticate(credentials):
        // OAuth logic
        
CLASS: AuthenticationContext
    strategy: AuthenticationStrategy
    
    executeAuthentication(credentials):
        RETURN strategy.authenticate(credentials)
2. Observer Pattern
CLASS: EventEmitter
    listeners: Map<eventName, List<callback>>
    
    on(eventName, callback):
        IF NOT listeners.has(eventName) THEN
            listeners.set(eventName, [])
        END IF
        listeners.get(eventName).append(callback)
    
    emit(eventName, data):
        IF listeners.has(eventName) THEN
            FOR EACH callback IN listeners.get(eventName) DO
                callback(data)
            END FOR
        END IF

Pseudocode Best Practices

  1. Language Agnostic: Don't use language-specific syntax
  2. Clear Logic: Focus on algorithm flow, not implementation details
  3. Handle Edge Cases: Include error handling in pseudocode
  4. Document Complexity: Always analyze time$space complexity
  5. Use Meaningful Names: Variable names should explain purpose
  6. Modular Design: Break complex algorithms into subroutines

Deliverables

  1. Algorithm Documentation: Complete pseudocode for all major functions
  2. Data Structure Definitions: Clear specifications for all data structures
  3. Complexity Analysis: Time and space complexity for each algorithm
  4. Pattern Identification: Design patterns to be used
  5. Optimization Notes: Potential performance improvements

Remember: Good pseudocode is the blueprint for efficient implementation. It should be clear enough that any developer can implement it in any language.

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/agent-pseudocode of ruvnet/ruflo.

Open the folder on GitHubat commit de590e1

Used in 3 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in ruvnet/ruflo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Pseudocode next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Pseudocode compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Pseudocode this skillruvnet/ruflo74k3 repos~2.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 2 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Categories

Questions about Agent Pseudocode

What does Agent Pseudocode do?

Agent skill for pseudocode - invoke with $agent-pseudocode. An agent skill from ruvnet/ruflo. Agent Pseudocode is an agent skill from ruvnet/ruflo.

When should I use Agent Pseudocode?

Agent Pseudocode fits situations like: development work in your project.

How do I install Agent Pseudocode in Claude Code?

Run `npx skills add ruvnet/ruflo --skill agent-pseudocode -a claude-code`. Or copy the skill folder (.agents/skills/agent-pseudocode in ruvnet/ruflo) into .claude/skills/agent-pseudocode in your project. Claude Code loads it when a task matches its description.

How do I install Agent Pseudocode in Codex?

Run `npx skills add ruvnet/ruflo --skill agent-pseudocode -a codex`. Or copy the skill folder (.agents/skills/agent-pseudocode in ruvnet/ruflo) into .agents/skills/agent-pseudocode in your project. Codex loads it when a task matches its description.

Can I use Agent Pseudocode in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/ruflo --skill agent-pseudocode -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-pseudocode, .gemini/skills/agent-pseudocode, .github/skills/agent-pseudocode and .opencode/skills/agent-pseudocode in your project.

What does Agent Pseudocode need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Pseudocode is instructions for the agent only.

Does Agent Pseudocode access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Pseudocode safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Pseudocode use?

Agent Pseudocode is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Pseudocode use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Pseudocode?

Skills that share tags, products or a category with Agent Pseudocode: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Pseudocode?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,012 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 7, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.