skills.rest
BekaChkhiro
BekaChkhiroCOMMUNITY
Explore all skills by this author →
GitHub

pfLogin

Authenticate PlanFlow accounts and store session tokens in config files.

1|Updated Jan 26, 2026
Search Tags:#API#CLI#config#login#token#authenticate#PlanFlow
One-click install
npx skills add https://github.com/BekaChkhiro/claude-plan-plugin --skill pflogin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pfLogin
Source: https://github.com/BekaChkhiro/claude-plan-plugin/tree/main/commands/pfLogin
Command: npx skills add https://github.com/BekaChkhiro/claude-plan-plugin --skill pflogin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PlanFlow users need a secure, convenient way to authenticate their PlanFlow account and manage credentials for CLI interactions.

Core Features & Use Cases

  • Interactive login: prompts for token and authorizes the PlanFlow CLI plugin.
  • Direct token input: allows you to provide an API token inline.
  • Credential storage: persists authentication details to the local/global config for auto-login.

Quick Start

Use the pfLogin command to authenticate with PlanFlow:

  • Interactive: /pfLogin
  • Direct token: /pfLogin pf_xxx...

Frequently Asked Questions about pfLogin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate with PlanFlow using an API token?▼

Authenticate with PlanFlow by providing an API token inline via the command line or using the interactive login prompt to authorize the PlanFlow CLI plugin and securely store your session token.

How does PlanFlow login persist credentials across sessions?▼

PlanFlow login persists credentials by validating tokens against the API and storing authentication details in local and global configuration files, specifically updating the plan-plugin config at ~/.config/claude/plan-plugin-config.json.

Can I use direct token input instead of interactive login for PlanFlow?▼

Yes, you can use direct token input for PlanFlow by passing the API token inline with the login command, bypassing the interactive prompts while still validating the token and persisting the session credentials.

Does PlanFlow login support custom configuration files and language settings?▼

PlanFlow login reads local and global configuration files, uses the configured language for interactive prompts, and updates the plan-plugin config at ~/.config/claude/plan-plugin-config.json to persist your authentication details.

Why does my PlanFlow CLI session require authentication?▼

Your PlanFlow CLI session requires authentication to securely validate your account credentials against the API, ensuring authorized access and enabling auto-login through persisted session tokens stored in your configuration files.

What is the best way to manage PlanFlow authentication tokens for CLI?▼

The best way to manage PlanFlow authentication tokens is using the login command to validate tokens against the API and persist credentials to the config file, allowing auto-login for future CLI interactions without re-entering tokens.

Related Skills

Explore More Software Engineering Skills→
BekaChkhiroBekaChkhiro
1

planSettingsLanguage

Switch Plan Plugin language preferences across global and local scopes.

Community
Basic
BekaChkhiroBekaChkhiro
1

pfCloudList

List cloud projects from PlanFlow using the PlanFlow API with an API token.

Community
Intermediate
BekaChkhiroBekaChkhiro
1

pfSyncPull

Pulls PlanFlow cloud plan into local PROJECT_PL.md via authenticated API request.

Community
Intermediate
mdmagnuson-creatormdmagnuson-creator

auth-headless

Inject session data into Playwright browser contexts for UI-free authentication.

Community
Advanced