ibank-team-staffing

Generate compliant iBank staffing plans for tb_user_team and tb_team_admin entries.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-team-staffing-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ibank-team-staffing
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/ibank-team-staffing
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-team-staffing-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of assigning iBank team members while adhering to strict fixed user ID structures, department ownership rules, and primary membership requirements, saving administrative teams hours of planning time.

Core Features & Use Cases

  • Rule-Compliant Staffing: Automatically assigns 4-9 team members per iBank staffing guidelines, including exactly one active leader, 1-3 cross-department collaborators, and optional department head oversight.
  • Structured Output Generation: Produces ready-to-use plans for tb_user_team and tb_team_admin entries, including user IDs, role flags, team roles, and allocation details.
  • Use Case: When you have an iBank team brief for the risk management department, use this Skill to generate a fully compliant staffing plan that aligns with the fixed user ID structure and persona roster requirements.

Quick Start

Use the ibank-team-staffing skill to generate a compliant team staffing plan for your iBank team brief, including all required tb_user_team and tb_team_admin entries.

Frequently Asked Questions about ibank-team-staffing

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

FAQPage Schema
How do I automate iBank team staffing and generate compliant tb_user_team entries?

To automate iBank team staffing, use this Skill to process team briefs and generate compliant tb_user_team entries with correct user IDs, role flags, and department allocation details based on fixed user ID structures.

What are the iBank team member allocation rules for department ownership and cross-department collaborators?

iBank team staffing rules require 4-9 members per team, exactly one active leader, 1-3 cross-department collaborators, and correct department ID mapping for team ownership to ensure compliant department allocation.

How do I create a tb_team_admin planning document from a team MD file?

You can generate a tb_team_admin planning document by feeding a team MD file or team brief into this Skill, which outputs structured admin planning entries including user IDs and role assignments.

Can I use this Skill for team admin planning if my team brief has optional department head oversight?

Yes, this Skill handles team admin planning with optional department head oversight, enforcing primary membership requirements and single active leader assignment while processing your fixed user ID structures.

Why does my iBank team staffing plan fail the primary membership requirements check?

Team staffing plans fail primary membership checks when user ID mapping is incorrect or team size limits are violated. This Skill enforces strict 4-9 member limits and single active leader rules to prevent such errors.

What's the best way to map fixed user IDs to department IDs for iBank team ownership?

The best way to map user IDs to department IDs is using this Skill's rule-compliant staffing engine, which validates fixed user ID structures against department ownership rules and outputs ready-to-use tb_user_team plans.