Introduction¶

When teachers apply for research projects, the issue is often not a lack of writing ability, but a fragmented process: knowing when to select which topic, what sections constitute a proposal, how to match research methods, the differences between municipal and provincial application requirements, and what materials are required for project completion. This knowledge is scattered across various educational research notifications and duplicated across tasks. Correspondingly, the pain point for developers is that project-related requests from users in conversations have broad semantic boundaries and are easily confused with class management strategies, lesson evaluation, or lesson plan writing. The Skill must first delineate its trigger scope before deciding whether to provide free assistance or initiate a paid workflow.

The Skill introduced below solidifies this workflow: basic services are completed locally and instantly, while templates and downloadable documents utilize Alipay pay-per-use billing.

What is this¶

Teacher Project Application Assistant PRO, coordinates @user_fca2c9bd/teacher-topic-application-pro, version 1.0.0, sourced from the community, categorized under education, published by user_fca2c9bd. It targets users who request project applications, project research, proposals, project approval, thesis proposals (opening reports), mid-term inspections, final reports, or educational research projects within conversations. It provides topic selection, proposal frameworks, research methods, end-to-end guidance, and compliance reminders.

In the current data, the rating is 100000, downloads are 2005, and installations are 0. Tags include pricing_type=alipay and requires_api_key=false.

Core Functions¶

The functionality is divided into two layers; this distinction is the primary design of the Skill.

Basic Services are completed locally and instantly without external calls, covering five areas: project topic selection, proposal frameworks, research methods, end-to-end guidance, and compliance reminders.

Paid Services cover scenarios requiring “applicable deliverables”: reusable proposal templates, writing demonstrations, reference topics, official notification matching, and downloadable proposal documents. These utilize Alipay AI Pay-Per-Use (AIPay / A2M) billing on a per-request basis.

The interaction on the payment side follows a clear protocol behavior, not implicit billing:

1. The server returns HTTP 402 for requests lacking valid payment credentials.
2. Billing information is placed in the Payment-Needed response header.
3. The buyer retries the same request with a Payment-Proof to retrieve the results.

In other words, the caller first receives the 402 and billing headers, then decides whether to pay and retry. This must be handled during integration; one cannot assume the request will simply succeed or error out.

Installation and Activation¶

The retrieved data does not provide CLI installation commands or configuration file fields, containing only coordinates and official URLs. Before activation, please visit the official page to confirm the current installation method; do not copy third-party commands blindly.

Official URL:

https://api.skillhub.cn/user_fca2c9bd/teacher-topic-application-pro

SkillHub Page:

https://www.skillhub.cn/skills/user_fca2c9bd/teacher-topic-application-pro

Coordinates:

@user_fca2c9bd/teacher-topic-application-pro

Two details are directly relevant to integration: requires_api_key=false, indicating that no API Key is needed for installation or basic services; pricing_type=alipay, indicating that payments are handled via Alipay pay-per-use, corresponding to the AIPay / A2M flow described above. Differences between Cursor, Codex CLI, and Claude Code are not specified in the materials and are omitted here.

Typical Usage¶

Triggering relies on user input. Trigger words cover: project application, project research, proposal, project approval, thesis proposal, mid-term inspection, final report, educational research project, as well as direct statements like “Help me write a project proposal,” “How to select a topic,” “What to watch for during project approval,” “How to apply for municipal/provincial projects,” and “What research methods are available.”

A complete workflow generally follows these steps:

1. The user asks, “How do I apply for a municipal-level project?” The Skill determines this hits the trigger scope and first utilizes basic services to provide topic direction, proposal framework, research method suggestions, and process highlights for that level.
2. The user follows up with, “Give me a reusable proposal template.” This hits the paid service layer. Without valid payment credentials, the server returns HTTP 402.
3. The caller reads the Payment-Needed response header to obtain the bill, completes the Alipay pay-per-use payment, and retries with the Payment-Proof.
4. Upon successful retry, the template or downloadable document is retrieved.

When “official notification matching” is required, the logic is identical: the matching action itself belongs to the paid layer. If unpaid, it will similarly result in 402 + Payment-Needed.

Applicable Scenarios and Notes¶

This is suitable for integrators who already handle teacher project-related requests in conversations and need to distinguish between “free Q&A” and “paid deliverables.” If the caller does not intend to handle the 402 and retry logic, it is recommended to use only the free layer—specifically, triggering only the five items: topic selection, frameworks, methods, process, and compliance.

There are three clear exclusions: ghostwriting full proposals, guaranteeing project approval, and forging application materials. These three fall outside the scope of this Skill and should not be treated as fulfillable requests during integration.

Additionally, there is a batch of requests that clearly belong to other skills. The Skill’s positioning is to hand these over rather than process them: pure homeroom teacher class management strategies, lesson observation and evaluation, general teaching research paper writing (non-project related), as well as requests like “help me write a lesson plan,” “teaching reflection,” “class meeting design,” “lesson evaluation draft,” “lecture script,” “reading insights,” “teaching notes,” and “assignment design.” During integration, this boundary must be written as an explicit routing judgment; otherwise, project-related requests and teaching research writing requests will compete with each other.

Given the data shows 0 installations, 2005 downloads, and a rating of 100000, it is advisable to treat this as a new community-sourced Skill. Before going live, perform a test run of the entire 402 and Payment-Proof retry workflow.

Conclusion¶

The value of this Skill lies in separating the process issues of project application and payment issues into two layers: basic services are free, instant, and predictable; when templates and documents are needed, usage-based billing is completed using three clear protocol elements: HTTP 402, Payment-Needed, and Payment-Proof. Before integration, two things need to be confirmed: the installation method on the official page, and whether the caller has implemented the payment credential retry logic.

Official URL: https://api.skillhub.cn/user_fca2c9bd/teacher-topic-application-pro