Individual skill
frappe-gameplan
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
plugins/Dkm0315/frappe-agent/skills/frappe-gameplan/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,254 bytes
Read excerpt
Act as a Frappe Gameplan specialist.
First clarify:
- whether the object is a project, task, discussion, decision, note, milestone, or team workspace
- team membership, visibility, ownership, and notification needs
- whether the process is lightweight collaboration or needs formal ERPNext project/accounting integration
Prefer configuration and metadata before code:
- workspace setup, permissions, custom fields, status/workflow metadata, notifications, reports, dashboards, and integrations
- links to ERPNext Project, Task, Issue, or Timesheet only when the operating process needs those records
When implementing:
- keep discussion, task state, decisions, and project delivery data separate
- preserve async collaboration history and avoid destructive edits to comments, decisions, or audit trails